View TE28F128J3D_1907707.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

intel? embedded flash memory (j3 v. d) (32, 64, and 128 mbit) datasheet product features the intel? embedded flash memory j3 version d (j3 v. d) provides improved mainstream performance with enhanced security features, taking advantage of the high quality and reliability of the nor-based intel 0.13 m etox? viii process technology. offered in 128-mbit (16-mbyte), 64-mbit, and 32-mbit densities, the j3 v. d device brings reliable, low-voltage capability (3 v read, program, and erase) with high speed, low-power operation. the j3 v. d device takes advantage of the proven manufacturing experience and is ideal for code and data applications where high density and low cost are required, such as in networking, telecommunications, digital set top boxes, audio recording, and digital imaging. intel flash memory components also deliver a new generation of forward-compatible software support. by using the common flash interface (cfi) and scalable command set (scs), customers can take advantage of density upgrades and optimized write capabilities of future intel? flash memory devices. architecture ?high-density symmetrical 128-kbyte blocks ?128 mbit (128 blocks) ?64 mbit (64 blocks) ?32 mbit (32 blocks) performance ?75 ns initial access speed (128/64/32 -mbit densities) ?25 ns 8-word and 4-word asynchronous page-mode reads ?32-byte write buffer ?4 s per byte effective programming time system voltage and power ?v cc = 2.7 v to 3.6 v ?v ccq = 2.7 v to 3.6 v security ? enhanced security options for code protection ? 128-bit protection register ?64-bit unique device identifier ?64-bit user-programmable otp cells ? absolute protection with v pen = gnd ? individual block locking ? block erase/program lockout during power transitions software ? program and erase suspend support ? flash data integrator (fdi), common flash interface (cfi) compatible quality and reliability ? operating temperature: -40 c to +85 c ? 100k minimum erase cycles per block ? 0.13 m etox? viii process packaging ? 56-lead tsop package ? 64-ball intel ? easy bga package 308551- 003 feburary 2006 notice: this document contains information on new products in production. the specifications are subject to change without notice. verify with your local intel sales office that you have the latest datasheet before finalizing a design. .com .com .com 4 .com u datasheet
2 datasheet information in this document is provided in connection with intel? products. no license, express or implied, by estoppel or otherwise, to any intellectual property righ ts is granted by this document. except as provided in intel's terms and conditions of sale for such products, intel assu mes no liability whatsoever, and intel disclaims any express or implied warranty, relating to sale and/or use of intel product s including liability or warranties relating to fitness for a particular purpose, merchantability, or infringeme nt of any patent, copyright or other intellectual property right. intel products are not intended for use in medical, life saving, or life sustaining applications. intel may make changes to specifications and product descriptions at any time, without notice. designers must not rely on the absence or characteristics of any features or instructions marked ?reserved? or ?undefined.? int el reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. the intel? embedded flash memory (j3 v. d) may contain design defects or errors known as errata which may cause the product to deviate from published specifications. current characterized errata are available on request. contact your local intel sales office or your distributor to obtain the latest specifications and before placing your product o rder. copies of documents which have an ordering number and are referenced in this document, or other intel literature may be obtaine d by calling 1-800- 548-4725 or by visiting intel's website at http://www.intel.com. copyright ? 2006, intel corporation. all rights reserved. intel and etox are trademarks or registered trademarks of intel corporation or its subsidiaries in the united states and other countries. *other names and brands may be claimed as the property of others. .com .com .com .com 4 .com u datasheet
datasheet 3 contents 1.0 introduction ..................................................................................................................6 1.1 nomenclature ........................................................................................................6 1.2 acronyms...............................................................................................................6 1.3 conventions...........................................................................................................6 2.0 functional overview .................................................................................................8 2.1 block diagram ..................................................................................................... 10 2.2 memory map........................................................................................................ 11 3.0 package information ...............................................................................................12 3.1 56-lead tsop package...................................................................................... 12 3.2 easy bga package ............................................................................................. 13 4.0 ballouts and signal descriptions ...................................................................... 15 4.1 easy bga ballout (32/64/128 mbit) .....................................................................15 4.2 56-lead tsop package pinout (32/64/128 mbit) ............................................... 16 4.3 signal descriptions .............................................................................................. 17 5.0 maximum ratings and operating conditions ............................................... 19 5.1 absolute maximum ratings ................................................................................. 19 5.2 operating conditions........................................................................................... 19 5.3 power up/down...................................................................................................20 5.3.1 power-up/down characteristics............................................................. 20 5.3.2 power supply decoupling....................................................................... 20 5.4 reset ...................................................................................................................20 6.0 electrical characteristics ...................................................................................... 21 6.1 dc current specifications ................................................................................... 21 6.2 dc voltage specifications.................................................................................... 22 6.3 capacitance.........................................................................................................23 7.0 ac characteristics ...................................................................................................24 7.1 read specifications ............................................................................................. 25 7.2 write specifications ............................................................................................. 28 7.3 program, erase, block-lock specifications......................................................... 30 7.4 reset specifications ............................................................................................31 7.5 ac test conditions.............................................................................................. 32 8.0 bus interface .............................................................................................................. 33 8.1 bus reads ........................................................................................................... 34 8.1.1 asynchronous page mode read ............................................................ 34 8.1.1.1 enhanced configuration register (ecr)...................................34 8.1.2 output disable ........................................................................................35 8.2 bus writes ........................................................................................................... 35 8.3 standby................................................................................................................36 8.3.1 reset/power-down................................................................................. 36 8.4 device commands .............................................................................................. 36 .com .com .com .com 4 .com u datasheet
4 datasheet 9.0 flash operations ...................................................................................................... 38 9.1 status register .................................................................................................... 38 9.1.1 clearing the status register................................................................... 39 9.2 read operations ................................................................................................. 39 9.2.1 read array ............................................................................................. 39 9.2.2 read status register ............................................................................. 40 9.2.3 read device information ........................................................................ 40 9.2.4 cfi query ............................................................................................... 41 9.3 programming operations .................................................................................... 41 9.3.1 single-word/byte programming ............................................................. 41 9.3.2 buffered programming ........................................................................... 42 9.4 block erase operations....................................................................................... 43 9.5 suspend and resume ......................................................................................... 44 9.6 status signal (sts) ............................................................................................. 45 9.7 security and protection ....................................................................................... 46 9.7.1 normal block locking............................................................................. 46 9.7.2 configurable block locking .................................................................... 47 9.7.3 otp protection registers....................................................................... 47 9.7.4 reading the otp protection register .................................................... 48 9.7.5 programming the otp protection register ............................................ 48 9.7.6 locking the otp protection register ..................................................... 48 9.7.7 vpp/ vpen protection ........................................................................... 50 appendix a device command codes ................................................................................. 51 appendix b j3 v. d id codes .................................................................................................. 52 appendix c flow charts ........................................................................................................... 53 c.1 write to buffer...................................................................................................53 c.2 status register .................................................................................................54 c.3 byte/word programming ..................................................................................55 c.4 program suspend/resume ..............................................................................56 c.5 block erase.......................................................................................................57 c.6 block erase suspend/resume .........................................................................58 c.7 block locking....................................................................................................59 c.8 unlock block .....................................................................................................60 c.9 otp protection register programming ............................................................61 appendix d common flash interface ................................................................................. 62 d.2 query structure overview ................................................................................63 d.3 block status register .......................................................................................64 d.4 cfi query identification string..........................................................................64 d.5 system interface information............................................................................65 d.6 device geometry definition..............................................................................66 d.7 primary-vendor specific extended query table ..............................................67 appendix e additional information ...................................................................................... 69 appendix f ordering information ......................................................................................... 70 .com .com .com .com 4 .com u datasheet
datasheet 5 revision history date of revision version description july 2005 001 - initial release september 2005 002 - marketing name was changed from 28fxxxj3 to j3 v. d - table 18 ?command bus operations for j3 v. d? on page 37 was updated - section 9.2.2, ?read status register? on page 40 - section 9.3.2, ?buffered programming? on page 42 - table 27 ?valid commands during suspend? on page 44 - table 28 ?sts configuration register? on page 45 was added february 2006 003 - section 5.3.1, ?power-up/down characteristics? on page 20 was modified - notes on table 8 ?dc voltage characteristics? on page 22 were updated - table 10 ?read operations? on page 25 was updated with r16 value - table 12 ?configuration performance? on page 30 was updated - note 1 of table 29 ?sts configuration coding definitions? on page 46 was updated .com .com .com .com 4 .com u datasheet
6 datasheet 1.0 introduction this document contains information pertaining to the intel? embedded flash memory (j3 v. d) device features, operation, and specifications. 1.1 nomenclature 1.2 acronyms 1.3 conventions h: hexadecimal affix k (noun): 1,000 m (noun): 1,000,000 nibble 4 bits byte: 8 bits amin: all densities amin = a0 for x8 all densities amin = a1 for x16 amax: 32 mbit amax = a21 64 mbit amax = a22 128 mbit amax = a23 block: a group of flash cells that share common erase circuitry and erase simultaneously clear: indicates a logic zero (0) program: to write data to the flash array set: indicates a logic one (1) vpen: refers to a signal or package connection name v pen : refers to timing or voltage levels cui: command user interface otp: one time programmable plr: protection lock register pr: protection register prd: protection register data rfu: reserved for future use sr: status register srd: status register data wsm: write state machine ecr: enhanced configuration register .com .com .com .com 4 .com u datasheet
7 datasheet word: 16 bits kword: 1,024 words kb: 1,024 bits kb: 1,024 bytes mb: 1,048,576 bits mb: 1,048,576 bytes brackets: square brackets ([]) will be used to designate group membership or to define a group of signals with similar function (i.e. a[21:1], sr[4,1] and d[15:0]). 00ffh: denotes 16-bit hexadecimal numbers 00ff 00ffh: denotes 32-bit hexadecimal numbers dq[15:0]: data i/o signals .com .com .com .com 4 .com u datasheet
8 datasheet 2.0 functional overview product description the intel? embedded flash memory (j3 v. d) family contains high-density memory organized in any of the following configurations: ? 16 mbytes or 8 mword (128-mbit), organized as one-hundred-twenty-eight 128-kbyte (131,072 bytes) erase blocks ? 8 mbytes or 4 mword (64-mbit), organized as sixty-four 128-kbyte erase blocks ? 4 mbytes or 2 mword (32-mbit), organized as thirty-two 128-kbyte erase blocks these devices can be accessed as 8- or 16-bit words. see figure 1, ?j3 v. d memory block diagram? on page 10 for further details. a 128-bit protection register has multiple uses, including unique flash device identification. the intel? embedded flash memory (j3 v. d) device includes new security features that were not available on the (previous) 0.25 m and 0.18 m versions of the j3 family. these new security features prevent altering of code through different protection schemes that can be implemented, based on user requirements. the j3 v. d device optimized architecture and interface dramatically increases read performance by supporting page-mode reads. this read mode is ideal for non-clock memory systems. a common flash interface (cfi) permits software algorithms to be used for entire families of devices. this allows device-independent, jedec id-independent, and forward- and backward- compatible software support for the specified flash device families. flash vendors can standardize their existing interfaces for long-term compatibility. scalable command set (scs) allows a single, simple software driver in all host systems to work with all scs-compliant flash memory devices, independent of system-level packaging (e.g., memory card, simm, or direct-to-board placement). additionally, scs provides the highest system/device data transfer rates and minimizes device and system-level implementation costs. a command user interface (cui) serves as the interface between the system processor and internal operation of the device. a valid command sequence written to the cui initiates device automation. an internal write state machine (wsm) automatically executes the algorithms and timings necessary for block erase, program, and lock-bit configuration operations. a block erase operation erases one of the device?s 128-kbyte blocks typically within one second, independent of other blocks. each block can be independently erased 100,000 times. block erase suspend mode allows system software to suspend block erase to read or program data from any other block. similarly, program suspend allows system software to suspend programming (byte/ word program and write-to-buffer operations) to read data or execute code from any other block that is not being suspended. each device incorporates a write buffer of 32 bytes (16 words) to allow optimum programming performance. by using the write buffer, data is programmed in buffer increments. .com .com .com .com 4 .com u datasheet
9 datasheet blocks are selectively and individually lockable in-system. individual block locking uses block lock-bits to lock and unlock blocks. block lock-bits gate block erase and program operations. lock-bit configuration operations set and clear lock-bits (using the set block lock-bit and clear block lock-bits commands). the status register indicates when the wsm?s block erase, program, or lock-bit configuration operation is finished. the sts (status) output gives an additional indicator of wsm activity by providing both a hardware signal of status (versus software polling) and status masking (interrupt masking for background block erase, for example). status indication using sts minimizes both cpu overhead and system power consumption. when configured in level mode (default mode), it acts as a ry/ by# signal. when low, sts indicates that the wsm is performing a block erase, program, or lock- bit configuration. sts-high indicates that the wsm is ready for a new command, block erase is suspended (and programming is inactive), program is suspended, or the device is in reset/power- down mode. additionally, the configuration command allows the sts signal to be configured to pulse on completion of programming and/or block erases. three ce signals are used to enable and disable the device. a unique ce logic design (see table 15, ?chip enable truth table? on page 33 ) reduces decoder logic typically required for multi-chip designs. external logic is not required when designing a single chip, a dual chip, or a 4- chip miniature card or simm module. the byte# signal allows either x8 or x16 read/writes to the device: ? byte#-low enables 8-bit mode; address a0 selects between the low byte and high byte. ? byte#-high enables16-bit operation; address a1 becomes the lowest order address and address a0 is not used (don?t care). figure 1, ?j3 v. d memory block diagram? on page 10 shows a device block diagram. when the device is disabled (see table 15, ?chip enable truth table? on page 33 ), with cex at vih and rp# at vih, the standby mode is enabled. when rp# is at vil, a further power-down mode is enabled which minimizes power consumption and provides write protection during reset. a reset time (tphqv) is required from rp# going high until data outputs are valid. likewise, the device has a wake time (tphwl) from rp#-high until writes to the cui are recognized. with rp# at vil, the wsm is reset and the status register is cleared. .com .com .com .com 4 .com u datasheet
10 datasheet 2.1 block diagram figure 1. j3 v. d memory block diagram 32-mbit: thirty-two 64-mbit: sixty-four 128-mbit: one-hundred twenty -eight 128-kbyte blocks input buffer output la tch/multi pl exer y-gating program/erase voltage switch data comparator status register identifier register data register i/o logic address latch address counter x-decoder y-decoder input buffer output buffer gnd v cc v pen ce 0 ce 1 ce 2 we # oe# rp # byte# command user interface 32-mbit: a 0 -a 21 64-mbit: a 0 -a 22 128-mbit: a 0 -a 23 dq 0 -dq 15 v cc write buffer write state machine multiplexer query sts v ccq ce logic a 0 -a 2 .com .com .com .com 4 .com u datasheet
11 datasheet 2.2 memory map figure 2. j3 v. d memory map 64-kword block 64-kword block 64-kword block 64-kword block word wide (x16) mode 1fffff 1f0000 7fffff 7f0000 01ffff 010000 00ffff 000000 128-kbyte block 128-kbyte block 128-kbyte block 128-kbyte block byte-wide (x8) mode 03fffff 03e0000 0ffffff 0fe0000 003ffff 0020000 001ffff 0000000 32-mbit 64-mbit 64-kword block 3fffff 3f0000 128-kbyte block 07fffff 07e0000 31 1 0 127 63 31 1 0 127 63 128-mbit a [23-1]: 128 mbit a [22-1]: 64 mbit a [21-1]: 32 mbit a [23-0]:128 mbit a [22-0]: 64 mbit a [21-0]: 32 mbit .com .com .com .com 4 .com u datasheet
12 datasheet 3.0 package information 3.1 56-lead tsop package figure 3. 56-lead tsop package mechanical table 1. 56-lead tsop dimension table (sheet 1 of 2) millimeters inches sym min nom max min nom max package height a 1.200 0.047 standoff a 1 0.050 0.002 package body thickness a 2 0.965 0.995 1.025 0.038 0.039 0.040 lead width b 0.100 0.150 0.200 0.004 0.006 0.008 lead thickness c 0.100 0.150 0.200 0.004 0.006 0.008 package body length d 1 18.200 18.400 18.600 0.717 0.724 0.732 package body width e 13.800 14.000 14.200 0.543 0.551 0.559 lead pitch e 0.500 0.0197 terminal dimension d 19.800 20.00 20.200 0.780 0.787 0.795 lead tip length l 0.500 0.600 0.700 0.020 0.024 0.028 lead count n 56 56 a 0 l detail a y d c z pin 1 e d 1 b detail b see detail a e see detail b a 1 seating plane a 2 see note 2 see notes 1 and 3 .com .com .com .com 4 .com u datasheet
13 datasheet 3.2 easy bga package lead tip angle 0 3 5 0 3 5 seating plane coplanarity y 0.100 0.004 lead to package offset z 0.150 0.250 0.350 0.006 0.010 0.014 table 1. 56-lead tsop dimension table (sheet 2 of 2) millimeters inches sym min nom max min nom max figure 4. easy bga mechanical specifications e seating plane s1 s2 e top view - ball side down bottom view - ball side up y a a1 d ball a1 corner a2 note: drawing not to scale a b c d e f g h 87654321 8 7 6 5 4 3 2 1 a b c d e f g h b ball a1 corner .com .com .com .com 4 .com u datasheet
14 datasheet notes: 1. for daisy chain evaluation unit info rmation refer to the intel flash memory packaging technology web page at: www.intel.com/design/packtech/index.htm 2. for packaging shipping media information refer to the intel flash memory packaging technology web page at: www.intel.com/ design/packtech/index.htm table 2. easy bga package dimensions table millimeters inches symbol min nom max notes min nom max package height a 1.200 0.0472 ball height a1 0.250 0.0098 package body thickness a2 0.780 0.0307 ball (lead) width b 0.330 0.430 0.530 0.0130 0.0169 0.0209 package body width (32 mb, 64 mb, 128 mb) d 9.900 10.000 10.100 1 0.3898 0.3937 0.3976 package body length (32 mb, 64 mb, 128 mb) e 12.900 13.000 13.100 1 0.5079 0.5118 0.5157 pitch [e] 1.000 0.0394 ball (lead) count n 64 64 seating plane coplanarity y 0.100 0.0039 corner to ball a1 distance along d (32/64/128 mb) s1 1.400 1.500 1.600 1 0.0551 0.0591 0.0630 corner to ball a1 distance along e (32/64/128 mb) s2 2.900 3.000 3.100 1 0.1142 0.1181 0.1220 .com .com .com .com 4 .com u datasheet
15 datasheet 4.0 ballouts and signal descriptions intel? embedded flash memory (j3 v. d) is available in two package types. each density of the j3 v. d is supported on both 64-ball easy bga and 56-lead thin small outline package (tsop) packages. figure 5 , and figure 6 show the pinouts. 4.1 easy bga ballout (32/64/128 mbit) notes: 1. address a22 is only valid on 64-mbit densities and above, otherwise, it is a no connect (nc). 2. address a23 is only valid on 128-mbit densities and above, otherwise, it is a no connect (nc). figure 5. easy bga ballout (32/64/128 mbit) 1 8 234 5 67 1 8 2 3 4 5 6 7 h g f e d c b a h g f e d c a a2 vss a9 a14 ce0# a19 ce1# rfu ce2# rfu vcc d13 vss d7 rfu vss a3 a7 a10 a15 a12 a20 a21 rfu a4 a5 a11 rfu rp# a16 a17 rfu sts d8 d1 d9 d4 d3 d15 rfu byte# oe# d0 d10 d12 d11 rfu rfu we# a23 a0 d2 d5 vccq d14 d6 a1 a6 a8 a13 vpen a18 a22 vcc a23 a4 a5 a11 rfu rp# a16 a17 rfu a1 a6 a8 a13 vpen a18 a22 vcc a3 a7 a10 a15 a12 a20 a21 rfu sts d8 d1 d9 d4 d3 d15 rfu byte# oe# d0 d10 d12 d11 rfu rfu we# a0 d2 d5 vccq d14 d6 a2 vss a9 a14 ce0# a19 ce1# rfu ce2# rfu vcc d13 vss d7 rfu vss b easy bga bottom view- ball side up intel? embedded flash memory (28fxxxj3d) easy bga top view- ball side down intel? embedded flash memory (28fxxxj3d) 32/64/128 mbit 32/64/128 mbit .com .com .com .com 4 .com u datasheet
16 datasheet 4.2 56-lead tsop package pinout (32/64/128 mbit) notes: 1. a22 exists on 64- and 128- densities. on 32-mbit density this signal is a no-connect (nc). 2. a23 exists on 128-mbit densities. on 32- and 64-mbit densities this signal is a no-connect (nc) figure 6. 56-lead tsop package pinout (32/64/128 mbit) 1 3 4 2 5 7 8 6 9 11 12 10 13 15 16 14 17 19 20 18 21 23 24 22 25 27 28 26 56 54 53 55 52 50 49 51 48 46 45 47 44 42 41 43 40 38 37 39 36 34 33 35 32 30 29 31 a 22 a 21 a 20 ce 1 a 19 a 17 a 16 a 18 v cc a 14 a 13 a 15 a 12 v pen rp# ce 0 a 11 a 9 a 8 a 10 gnd a 6 a 5 a 7 a 4 a 2 a 1 a 3 rfu oe# sts we# dq 15 dq 14 dq 6 dq 7 gnd dq 5 dq 12 dq 13 dq 4 gnd dq 11 v ccq dq 3 dq 2 v cc dq 10 dq 9 dq 8 dq 0 dq 1 a 0 a 23 ce 2 byte# intel? embedded flash memory (28fxxxj3d) 56-lead tsop standard pinout 14 mm x 20 mm top view 32/64/128 mbit .com .com .com .com 4 .com u datasheet
17 datasheet 4.3 signal descriptions table 3 lists the active signals used on j3 v. d and provides a description of each. table 3. signal descriptions for j3 v. d (sheet 1 of 2) symbol type name and function a0 input byte-select address: selects between high and low byte when the device is in x8 mode. this address is latched during a x8 program cycle. not used in x16 mode (i.e., the a0 input buffer is turned off when byte# is high). a[max:1] input address inputs: inputs for addresses during read and pr ogram operations. addresses are internally latched during a program cycle: 32-mbit ? a[21:1] 64-mbit ? a[22:1] 128-mbit ? a[23:1] d[7:0] input/output low-byte data bus: inputs data during buffer writes and programming, and inputs commands during cui writes. outputs array, cfi, identifier, or status data in the appropriate read mode. data is internally latched during write operations. d[15:8] input/output high-byte data bus: inputs data during x16 buffer writ es and programming operations. outputs array, cfi, or identifier data in the appropriate read mode; not used for status register reads. data is internally latched during write oper ations in x16 mode. d[15-8] float in x8 mode ce[2:0] input chip enables: activate the 32-, 64- and 128 mbit devices? control logic, input buffers, decoders, and sense amplifiers. when the device is de-selected (see table 15, ?chip enable truth table? on page 33 ), power reduces to standby levels. all timing specifications are the same for these three signals. device selection occurs with the first edge of ce0#, ce1#, or ce2# that enables the device. device deselection occurs with the first edge of ce0#, ce1#, or ce2# that disables the device (see table 15, ?chip enable truth table? on page 33 ). rp# input reset: rp#-low resets internal automation and puts the device in power-down mode. rp#-high enables normal operation. exit from reset sets the device to read array mode. when driven low, rp# inhibits write operations which provi des data protection during power transitions. oe# input output enable: activates the device?s outputs through the data buffers during a read cycle. oe# is active low. we# input write enable: controls writes to the cui, the write buffer, and array blocks. we# is active low. addresses and data are latched on the rising edge of we#. sts open drain output status: indicates the status of the internal state machine. when configured in level mode (default), it acts as a ry/by# signal. when configured in one of its pulse modes, it can pulse to indicate program and/or erase completion. for alte rnate configurations of the status signal, see the configurations command and section 9.6, ?status signal (sts)? on page 45 . sts is to be tied to vccq with a pull-up resistor. byte# input byte enable: byte#-low places the device in x8 mode; data is input or output on d[7:0], while d[15:8] is placed in high-z. address a0 selects between the high and low byte. byte#-high places the device in x16 mode, and turns off the a0 input buffer. address a1 becomes the lowest-order address bit. vpen input erase / program / block lock enable: for erasing array blocks, programming data, or configuring lock-bits. with v pen v penlk , memory contents cannot be altered. vcc power core power supply: core (logic) source voltage. writes to the flash array are inhibited when v cc v lko . caution: device operation at invalid vcc voltages should not be attempted. vccq power i/o power supply: power supply for input/output buffers.this ball can be tied directly to v cc . .com .com .com .com 4 .com u datasheet
18 datasheet gnd supply ground: ground reference for device logi c voltages. connect to system ground. nc ? no connect: lead is not internally connected; it may be driven or floated. rfu ? reserved for future use: balls designated as rfu are reserved by intel for future device functionality and enhancement . table 3. signal descriptions for j3 v. d (sheet 2 of 2) symbol type name and function .com .com .com .com 4 .com u datasheet
19 datasheet 5.0 maximum ratings and operating conditions 5.1 absolute maximum ratings warning: stressing the device beyond the ?absolute maximum ratings? may cause permanent damage. these are stress ratings only. 5.2 operating conditions warning: operation beyond the ?operating conditions? is not recommended and extended exposure beyond the ?operating conditions? may affect device reliability notice: this document contains information available at the time of its release. the specifications are subject to change without notice. verify with your local intel sales office that you have the latest datasheet before finalizing a design . table 4. absolute maximum ratings parameter min max unit notes temperature under bias expanded (t a , ambient) ?40 +85 c ? storage temperature ?65 +125 c ? vcc voltage ?2.0 +5.6 v 2 vccq ?2.0 +5.6 v 2 voltage on any input/output signal (except vcc, vccq) ?2.0 v ccq (max) + 2.0 v 1 i sh output short circuit current ? 100 ma 3 notes: 1. voltage is referenced to v ss . during infrequent non-perio dic transitions, the voltage potential between v ss and input/output pins may undershoot to ?2.0 v for periods < 20 ns or overshoot to v ccq (max) + 2.0 v for periods < 20 ns. 2. during infrequent non-periodic transitions, the voltage potential between v cc and the supplies may undershoot to ? 2.0 v for periods < 20 ns or v supply (max) + 2.0 v for periods < 20 ns. 3. output shorted for no more than one second. no more than one output shorted at a time table 5. temperature and v cc operating condition of j3 v. d symbol parameter min max unit test condition t a -40.0 +85 c ambient temperature v cc v cc supply voltage 2.70 3.6 v ? v ccq v ccq supply voltage 2.70 3.6 v ? .com .com .com .com 4 .com u datasheet
20 datasheet 5.3 power up/down this section provides an overview of system level considerations with regards to the flash device. it includes a brief description of power-up, power-down and decoupling design considerations. 5.3.1 power-up/down characteristics to prevent conditions that could result in spurious program or erase operations, the power-up/ power-down sequence shown in table 6 is recommended. for dc voltage characteristics refer to table 8 . note that each power supply must reach its minimum voltage range before applying/ removing the next supply voltage. ? power supplies connected or sequenced together. device inputs must not be driven until all supply voltages reach their minimum range. rp# should be low during power transitions. 5.3.2 power supply decoupling when the device is enabled, many internal conditions change. circuits are energized, charge pumps are switched on, and internal voltage nodes are ramped. all of this internal activities produce transient signals. the magnitude of the transient signals depends on the device and system loading. to minimize the effect of these transient signals, a 0.1 f ceramic capacitor is required across each vcc/vss and vccq signal . capacitors should be placed as close as possible to device connections. additionally, for every eight flash devices, a 4.7 f electrolytic capacitor should be placed between vcc and vss at the power supply connection. this 4.7 f capacitor should help overcome voltage slumps caused by pcb (printed circuit board) trace inductance. 5.4 reset by holding the flash device in reset during power-up and power-down transitions, invalid bus conditions may be masked. the flash device enters reset mode when rp# is driven low. in reset, internal flash circuitry is disabled and outputs are placed in a high-impedance state. after return from reset, a certain amount of time is required before the flash device is able to perform normal operations. after return from reset, the flash device defaults to asynchronous page mode. if rp# is driven low during a program or erase operation, the program or erase operation will be aborted and the memory contents at the aborted block or address are no longer valid. see figure 12, ?ac waveform for reset operation? on page 30 for detailed information regarding reset timings. table 6. power-up/down sequence power supply voltage power-upsequence power-down sequence v cc(min) 1st 1st 1st ? sequencing not required ? 3rd 2nd 2nd ? sequencing not required ? v ccq(min) 2nd 2nd ? 2nd 1st ? v pen(min) 3rd 2nd 1st 1st .com .com .com .com 4 .com u datasheet
21 datasheet 6.0 electrical characteristics 6.1 dc current specifications table 7. dc current characteristics (sheet 1 of 2) v ccq 2.7 - 3.6v test conditions notes v cc 2.7 - 3.6v symbol parameter typ max unit i li input and v pen load current 1 a v cc = v cc max; v ccq = v ccq max v in = v ccq or v ss 1 i lo output leakage current 10 a v cc = v cc max; v ccq = v ccq max v in = v ccq or v ss 1 i ccs v cc standby current 50 120 a cmos inputs, v cc = v cc max; vccq = vccqmax device is disabled (see table 15, ?chip enable truth table? on page 33 ), rp# = v ccq 0.2 v 1,2,3 0.71 2 ma ttl inputs, v cc = v cc max, vccq = vccqmax device is disabled (see table 15, ?chip enable truth table? on page 33 ), rp# = v ih i ccd v cc power-down current 50 120 a rp# = gnd 0.2 v, i out (sts) = 0 ma i ccr v cc page mode read current 4- word page 15 20 ma cmos inputs, v cc = v cc max, v ccq = v ccq max device is enabled (see table 15, ?chip enable truth table? on page 33 ) f = 5 mhz, i out = 0 ma 1,3 24 29 ma cmos inputs,v cc = v cc max, v ccq = v ccq max device is enabled (see table 15, ?chip enable truth table? on page 33 ) f = 33 mhz, i out = 0 ma 8- word page 10 15 ma cmos inputs, v cc = v cc max, v ccq = v ccq max using standard 8 word page mode reads. device is enabled (see table 15, ?chip enable truth table? on page 33 ) f = 5 mhz, i out = 0 ma 30 54 ma cmos inputs,v cc = v cc max, v ccq = v ccq max using standard 8 word page mode reads. device is enabled (see table 15, ?chip enable truth table? on page 33 ) f = 33 mhz, i out = 0 ma density: 128-, 64-, and 32- mbit i ccw v cc program or set lock-bit current 35 60 ma cmos inputs, v pen = v cc 1,4 40 70 ma ttl inputs, v pen = v cc .com .com .com .com 4 .com u datasheet
22 datasheet 6.2 dc voltage specifications i cce v cc block erase or clear block lock-bits current 35 70 ma cmos inputs, v pen = v cc 1,4 40 80 ma ttl inputs, v pen = v cc i ccws i cces v cc program suspend or block erase suspend current 10 ma device is enabled (see table 15, ?chip enable truth table? on page 33 ) 1,5 notes: 1. all currents are in rms unless otherwise noted. these currents are valid for all product versions (packages and speeds). contact intel?s application support hotline or your local sales office for information about typical specifications. 2. includes sts. 3. cmos inputs are either v cc 0.2 v or gnd 0.2 v. ttl inputs are either v il or v ih . 4. sampled, not 100% tested. 5. i ccws and i cces are specified with the device selected. if the device is read or written while in erase suspend mode, the device?s current draw is i ccr and i ccws . table 7. dc current characteristics (sheet 2 of 2) v ccq 2.7 - 3.6v test conditions notes v cc 2.7 - 3.6v symbol parameter typ max unit table 8. dc voltage characteristics (sheet 1 of 2) v ccq 2.7 - 3.6 v test conditions notes v cc 2.7 - 3.6 v symbol parameter min max unit v il input low voltage ?0.5 0.8 v 2, 5, 6 v ih input high voltage 2.0 v ccq + 0.5v v 2, 5, 6 v ol output low voltage 0.4 v v cc = v cc min v ccq = v ccq min i ol = 2 ma 1, 2 0.2 v v cc = v cc min v ccq = v ccq min i ol = 100 a v oh output high voltage 0.85 v ccq v v cc = v ccmin v ccq = v ccq min i oh = ?2.5 ma 1, 2 v ccq ? 0.2 v v cc = v ccmin v ccq = v ccq min i oh = ?100 a v penlk v pen lockout during program, erase and lock-bit operations 2.2 v 2, 3 .com .com .com .com 4 .com u datasheet
23 datasheet 6.3 capacitance notes: 1. sampled. not 100% tested. 2. t a = +25 c, f = 1 mhz v pen v pen during block erase, program, or lock-bit operations 2.7 3.6 v 3 v lko v cc lockout voltage 2.0 v 4 notes: 1. includes sts. 2. sampled, not 100% tested. 3. block erases, programming, and lock-bit configurations are inhibited when v pen v penlk , and not guaranteed in the range between v penlk (max) and v penh (min), and above v penh (max). 4. block erases, programming, and lock-bit configurations are inhibited when v cc < v lko , and not guaranteed in the range between v lko (min) and v cc (min), and above v cc (max). 5. includes all operational modes of the device including standby and power-up sequences 6. input/output signals can undershoot to -1.0v referenced to v ss and can overshoot to v ccq = 1.0v for duration of 2ns or less, the v ccq valid range is referenced to v ss . table 8. dc voltage characteristics (sheet 2 of 2) v ccq 2.7 - 3.6 v test conditions notes v cc 2.7 - 3.6 v symbol parameter min max unit table 9. j3 v. d capacitance symbol parameter 1 type max unit condition 2 c in input capacitance 6 8 pf v in = 0.0 v c out output capacitance 8 12 pf v out = 0.0 v .com .com .com .com 4 .com u datasheet
24 datasheet 7.0 ac characteristics timing symbols used in the timing diagrams within this document conform to the following convention: note: exceptions to this convention include tacc and tapa. tacc is a generic timing symbol that refers to the aggregate initial-access delay as determined by tavqv, telqv, and tglqv (whichever is satisfied last) of the flash device. tapa is specified in the flash device?s data sheet, and is the address-to-data delay for subsequent page-mode reads. signal code state code address a high h data - read q low l data - write d high-z z chip enable (ce#) e low-z x output enable (oe#) g valid v write enable (we#) w invalid i address valid (adv#) v reset (rst#) p clock (clk) c wait t e t l q v source signal target state source state target signal .com .com .com .com 4 .com u datasheet
25 datasheet 7.1 read specifications notes: ce x low is defined as the first edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 15, ?chip enable truth table? on page 33 ). 1. see ac input/output reference waveforms for the maximum allowable input slew rate. table 10. read operations asynchronous specifications v cc = 2.7 v?3.6 v (3) v ccq = 2.7 v?3.6 v (3) # sym parameter density -75 -95 unit notes min max min max r1 t avav read/write cycle time 32 mbit 75 ns 1,2 64 mbit 75 1,2 128 mbit 75 1,2 r2 t av qv address to output delay 32 mbit 75 ns 1,2 64 mbit 75 1,2 128 mbit 75 1,2 r3 t elqv ce x to output delay 32 mbit 75 ns 1,2 64 mbit 75 1,2 128 mbit 75 1,2 r4 t glqv oe# to non-array output delay 25 25 ns 1,2,4 r5 t phqv rp# high to output delay 32 mbit 150 ns 1,2 64 mbit 180 1,2 128 mbit 210 1,2 r6 t elqx ce x to output in low z all 0 0 ns 1,2,5 r7 t glqx oe# to output in low z 0 0 ns 1,2,5 r8 t ehqz ce x high to output in high z 25 25 ns 1,2,5 r9 t ghqz oe# high to output in high z 15 15 ns 1,2,5 r10 t oh output hold from address, ce x , or oe# change, whichever occurs first 0 0 ns 1,2,5 r11 t elfl/ t elfh ce x low to byte# high or low 10 10 ns 1,2,5 r12 t flqv/ t fhqv byte# to output delay 1 1 s1,2 r13 t flqz byte# to output in high z 1 1 s 1,2,5 r14 t ehel cex high to cex low all 0 0 ns 1,2,5 r15 t apa page address access time 25 25 ns 5, 6 r16 t glqv oe# to array output delay .com .com .com .com 4 .com u datasheet
26 datasheet 2. oe# may be delayed up to t elqv -t glqv after the first edge of ce0, ce1, or ce2 that enables the device (see table 15, ?chip enable truth table? on page 33 ) without impact on t elqv . 3. see figure 13, ?ac input/output reference waveform? on page 32 and figure 14, ?transient equivalent testing load circuit? on page 32 for testing characteristics. 4. sampled, not 100% tested. 5. for devices configured to standard word/byte read mode, r15 (t apa ) will equal r2 (t av qv ). notes: 1. ce x low is defined as the last edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 15, ?chip enable truth table? on page 33 ). 2. when reading the flash array a faster t glqv (r16) applies. for non-array reads, r4 applies (i.e., status register reads, query reads, or device identifier reads). figure 7. single word asynchronous read waveform r11 r5 r12 r13 r10 r4 r16 r7 r6 r9 r8 r3 r1 r2 r1 a ddress [a] cex [e] oe# [g] we# [w] data [d/q] byte#[f] rp# [p] .com .com .com .com 4 .com u datasheet
27 datasheet note: ce x low is defined as the last edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 15, ?chip enable truth table? on page 33 ). notes: 1. ce x low is defined as the last edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 15, ?chip enable truth table? on page 33 ). 2. in this diagram, byte# is asserted high figure 8. 4-word asynchronous page mode read waveform 00 01 10 11 1 2 3 4 r10 r15 r10 r5 r9 r8 r7 r6 r4 r3 r1 r2 r1 a [max:3] [a] a[2:1] [a] cex [e] oe# [g] we# [w] d[15:0] [q] rp# [p] figure 9. 8-word asynchronous page mode read 1 2 7 8 r10 r15 r10 r5 r9 r8 r7 r6 r4 r3 r1 r2 r1 a [max:4] [a] a[3:1] [a] cex [e] oe# [g] we# [w] d[15:0] [q] rp# [p] byte# .com .com .com .com 4 .com u datasheet
28 datasheet 7.2 write specifications table 11. write operations # symbol parameter density valid for all speeds unit notes min max w1 t phwl (t phel ) rp# high recovery to we# (ce x ) going low 32 mbit 150 ns 1,2,3 64 mbit 180 128 mbit 210 w2 t elwl (t wlel )ce x (we#) low to we# (ce x ) going low all 0 1,2,4 w3 t wp write pulse width 60 1,2,4 w4 t dvwh (t dveh ) data setup to we# (ce x ) going high 50 1,2,5 w5 t avw h (t aveh ) address setup to we# (ce x ) going high 55 1,2,5 w6 t wheh (t ehwh )ce x (we#) hold from we# (ce x ) high 0 1,2, w7 t whdx (t ehdx ) data hold from we# (ce x ) high 0 1,2, w8 t whax (t ehax ) address hold from we# (ce x ) high 0 1,2, w9 t wph write pulse width high 30 1,2,6 w11 t vpwh (t vpeh )v pen setup to we# (ce x ) going high 0 1,2,3 w12 t whgl (t ehgl ) write recovery before read 35 1,2,7 w13 t whrl (t ehrl )we# (ce x ) high to sts going low 500 1,2,8 w15 t qvvl v pen hold from valid srd, sts going high 0 1,2,3,8,9 notes: ce x low is defined as the first edge of ce0, ce1, or ce2 that enables the device. ce x high is defined at the first edge of ce0, ce1, or ce2 that disables the device (see table 15, ?chip enable truth table? on page 33 ). 1. read timing characteristics during block erase, progr am, and lock-bit configuration operations are the same as during read-only operations. refer to ac characteristics?read-only operations . 2. a write operation can be initiated and terminated with either ce x or we#. 3. sampled, not 100% tested. 4. write pulse width (t wp ) is defined from ce x or we# going low (whichever goes low last) to ce x or we# going high (whichever goes high first). hence, t wp = t wlwh = t eleh = t wleh = t elwh . 5. refer to table 16, ?enhanced configuration register? on page 35 for valid a in and d in for block erase, program, or lock-bit configuration. 6. write pulse width high (t wph ) is defined from ce x or we# going high (whichever goes high first) to ce x or we# going low (whichever goes low first). hence, t wph = t whwl = t ehel = t whel = t ehwl . 7. for array access, t avqv is required in addition to t whgl for any accesses after a write. 8. sts timings are based on sts configured in its ry/by# default mode. 9. v pen should be held at v penh until determination of block erase, program, or lock-bit configuration success (sr[1,3,4,5] = 0). .com .com .com .com 4 .com u datasheet
29 datasheet _ figure 10. asynchronous write waveform d w11 w1 w13 w7 w4 w9 w9 w3 w3 w2 w6 w8 w5 address [a] cex (we#) [e (w)] we # (ce x) [w (e)] oe# [g] data [d/q] sts[r] rp# [p] vpen [v] figure 11. asynchronous write to read waveform d w11 w1 w7 w4 w12 w3 w3 w2 w6 w8 w5 address [a] ce# [e] we# [w] oe# [g] data [d/q] rst #/ rp# [p] vpen [v] .com .com .com .com 4 .com u datasheet
30 datasheet 7.3 program, erase, block-lock specifications 7.4 reset specifications table 12. configuration performance # symbol parameter typ max (8) unit notes w16 write buffer byte program time (time to program 32 bytes/16 words) 128 654 s 1,2,3,4,5,6,7 w16 t whqv3 t ehqv3 byte program time (using word/byte program command) 40 175 s 1,2,3,4 block program time (using write to buffer command) 0.53 2.4 sec 1,2,3,4 w16 t whqv4 t ehqv4 block erase time 1.0 4.0 sec 1,2,3,4 w16 t whqv5 t ehqv5 set lock-bit time 50 60 s 1,2,3,4,9 w16 t whqv6 t ehqv6 clear block lock-bits time 0.5 0.70 sec 1,2,3,4,9 w16 t whrh1 t ehrh1 program suspend latency time to read 15 20 s 1,2,3,9 w16 t whrh t ehrh erase suspend latency time to read 15 20 s 1,2,3,9 wy t sts sts pulse width low time 500 ns 1 notes: 1. typical values measured at t a = +25 c and nominal voltages. assumes corresponding lock-bits are not set. subject to change based on device characterization. 2. these performance numbers are valid for all speed versions. 3. sampled but not 100% tested. 4. excludes system-level overhead. 5. these values are valid when the buffer is full, and the start address is aligned on a 32-byte boundary. 6. effective per-byte program time (t whqv1 , t ehqv1 ) is 4 s/byte (typical). 7. effective per-word program time (t whqv2 , t ehqv2 ) is 8 s/word (typical). 8. max values are measured at worst case temperature, data pattern and v cc corner after 100k cycles (except as noted). 9. max values are expressed at 25 c/-40 c. figure 12. ac waveform for reset operation p3 p1 p2 p1 sts (r) rp# (p) vcc .com .com .com .com 4 .com u datasheet
31 datasheet note: sts is shown in its default mode (ry/by#) table 13. reset specifications # symbol parameter min max unit notes p1 t plph rp# pulse low time (if rp# is tied to v cc , this specification is not applicable) 25 s1,2 p2 t phrh rp# high to reset during block erase, program, or lock-bit configuration 100 ns 1,3 p3 t vccph vcc power valid to rp# de-assertion (high) 60 s notes: 1. these specifications are valid for all product versions (packages and speeds). 2. if rp# is asserted while a block erase, progr am, or lock-bit configuration operation is not executing then the minimum required rp# pulse low time is 100 ns. 3. a reset time, t phqv , is required from the latter of sts (i n ry/by# mode) or rp# going high until outputs are valid. .com .com .com .com 4 .com u datasheet
32 datasheet 7.5 ac test conditions note: ac test inputs are driven at v ccq for a logic "1" and 0.0 v for a logic "0." input timing begins, and output timing ends, at v ccq /2 v (50% of v ccq ). input rise and fall times (10% to 90%) < 5 ns. note: c l includes jig capacitance figure 13. ac input/output reference waveform outpu t test points input v ccq /2 v ccq 0.0 v ccq /2 figure 14. transient equivalent testing load circuit device under test c l out test configuration c l (pf) v ccq = v ccqmin 30 .com .com .com .com 4 .com u datasheet
33 datasheet 8.0 bus interface this section provides an overview of bus operations. basically, there are three operations you can do with flash memory: read, program (write), and erase.the on-chip write state machine (wsm) manages all erase and program algorithms. the system cpu provides control of all in-system read, write, and erase operations through the system bus. all bus cycles to or from the flash memory conform to standard microprocessor bus cycles. table 14 summarizes the necessary states of each control signal for different modes of operations. notes: 1. see table 15 for valid ce x configurations. 2. oe# and we# should never be asserted simultaneously. if done so, oe# overrides we#. 3. dq refers to dq[7:0} when byte# is low and dq[15:0] if byte# is high. 4. refer to dc characteristics. when v pen v penlk , memory contents can be read but not altered. 5. x should be v il or v ih for the control pins and v penlk or v penh for v pen . for outputs, x should be v ol or v oh . 6. in default mode, sts is v ol when the wsm is executing internal block erase, program, or a lock-bit configuration algorithm. it is v oh (pulled up by an external pull up resistance ~= 10k) when the wsm is not busy, in block erase suspend mode (with programming inactive), program suspend mode, or reset power- down mode. 7. see table 18, ?command bus operations for j3 v. d? on page 37 for valid din (user commands) during a write operation 8. array writes are either pr ogram or erase operations. / the next few sections detail each of the basic flash operations and some of the advanced features available on flash memory. table 14. bus operations mode rp# ce x (1) oe# (2) we# (2) v pen dq 15:0 (3) sts (default mode) notes async., status, query and identifier reads v ih enabled v il v ih xd out high z 4,6 output disable v ih enabled v ih v ih x high z high z standby v ih disabled x x x high z high z reset/power-down v il x x x x high z high z command writes v ih enabled v ih v il xd in high z 6,7 array writes (8) v ih enabled v ih v il v penh xv il 8,5 table 15. chip enable truth table ce2 ce1 ce0 device v il v il v il enabled v il v il v ih disabled v il v ih v il disabled v il v ih v ih disabled v ih v il v il enabled v ih v il v ih enabled v ih v ih v il enabled v ih v ih v ih disabled note: for single-chip applications, ce2 and ce1 can be connected to gnd. .com .com .com .com 4 .com u datasheet
34 datasheet 8.1 bus reads reading from flash memory outputs stored information to the processor or chipset, and does not change any contents. reading can be performed an unlimited number of times. besides array data, other types of data such as device information and device status is available from the flash. to perform a bus read operation, cex (refer to table 15 on page 33 ) and oe# must be asserted. cex is the device-select control; when active, it enables the flash memory device. oe# is the data- output control; when active, the addressed flash memory data is driven onto the i/o bus. for all read states, we# and rp# must be de-asserted. see section 9.2, ?read operations? on page 39 . 8.1.1 asynchronous page mode read there are two asynchronous page mode configurations available on j3 v. d, depending on the system design requirements: ? four-word page mode: this is the default mode on power-up or reset. array data can be sensed up to four words (8 bytes) at a time. ? eight-word page mode: array data can be sensed up to eight words (16 bytes) at a time. this mode must be enabled on power-up or reset by using the command sequence described in table 18 on page 37 . address bits a[3:1] determine which word is output during a read operation, and a[3:0] determine which byte is output for a x8 bus width. after the initial access delay, the first word out of the page buffer corresponds to the initial address. in four-word page mode, address bits a[2:1] determine which word is output from the page buffer for a x16 bus width, and a[2:0] determine which byte is output from the page buffer for a x8 bus width. subsequent reads from the device come from the page buffer. these reads are output on d[15:0] for a x16 bus width and d[7:0] for a x8 bus width after a minimum delay as long as a[2:0] (four-word page mode) or a[3:0] (eight-word page mode). data can be read from the page buffer multiple times, and in any order. in four-word page mode, if address bits a[max:3] (a[max:4] for eight-word page mode) change at any time, or if ce# is toggled, the device will sense and load new data into the page buffer. asynchronous page mode is the default read mode on power-up or reset. to perform a page mode read after any other operation, the read array command must be issued to read from the flash array. asynchronous page mode reads are permitted in all blocks and are used to access register information. during register access, only one word is loaded into the page buffer. 8.1.1.1 enhanced configuration register (ecr) the enhanced configuration register (ecr) is a volatile storage register that when addressed by the set enhanced configuration register command can select between four-word page mode and eight-word page mode. the ecr is volatile; all bits will be reset to default values when rp# is deasserted or power is removed from the device. to modify ecr settings, use the set enhanced configuration register command. the set enhanced configuration register command is written along with the configuration register value, which is placed on the lower 16 bits of the address bus a[15:0]. this is followed by a second write that confirms the operation and again presents the enhanced configuration register data on the address bus. after executing this command, the device returns to read array mode. the ecr is shown in table 16 . 8-word page mode command bus-cycle is captured in table 17 . .com .com .com .com 4 .com u datasheet
35 datasheet note: for forward compatibility reasons, if the 8-word asynchronous page mode is used on j3 v. d, a clear status register command must be executed after issuing the set enhanced configuration register command. see table 17 for further details. 8.1.2 output disable with cex asserted, and oe# at a logic-high level (v ih ), the device outputs are disabled. output signals d[15:0] are placed in a high-impedance state. 8.2 bus writes writing or programming to the device, is where the host writes information or data into the flash device for non-volatile storage. when the flash device is programmed, ?ones? are changed to ?zeros?. ?zeros? cannot be programed back to ?ones?. to do so, an erase operation must be performed. writing commands to the command user interface (cui) enables various modes of operation, including the following: ? reading of array data ? common flash interface (cfi) data ? identifier codes, inspection, and clearing of the status register ? block erasure, program, and lock-bit configuration (when v pen = v penh ) erasing is performed on a block basis ? all flash cells within a block are erased together. any information or data previously stored in the block will be lost. erasing is typically done prior to programming. the block erase command requires appropriate command data and an address within the block to be erased. the byte/word program command requires the command and table 16. enhanced configuration register reserved page length reserved ecr 15 ecr 14 ecr 13 ecr 12 ecr 11 ecr 10 ecr 9 ecr 8 ecr 7 ecr 6 ecr 5 ecr 4 ecr 3 ecr 2 ecr 1 ecr 0 bits description notes ecr[15:14] rfu all bits should be set to 0. ecr[13] ? ?1? = 8 word page mode ? ?0? = 4 word page mode ecr[12:0] rfu all bits should be set to 0. table 17. j3 v. d asynchronous 8-word page mode command bus-cycle definition command bus cycles required first bus cycle second bus cycle oper addr (1) data oper addr (1) data set enhanced configuration register (set ecr) 2 write ecd 0060h write ecd 0004h 1. x = any valid address within the device. ecd = enhanced configuration register data .com .com .com .com 4 .com u datasheet
36 datasheet address of the location to be written. set block lock-bit commands require the command and block within the device to be locked. the clear block lock-bits command requires the command and address within the device to be cleared. the cui does not occupy an addressable memory location. it is written when the device is enabled and we# is active. the address and data needed to execute a command are latched on the rising edge of we# or the first edge of ce0, ce1, or ce2 that disables the device (see table 15 on page 33 ). standard microprocessor write timings are used. 8.3 standby ce0, ce1, and ce2 can disable the device (see table 15 on page 33 ) and place it in standby mode. this manipulation of cex substantially reduces device power consumption. d[15:0] outputs are placed in a high-impedance state independent of oe#. if deselected during block erase, program, or lock-bit configuration, the wsm continues functioning, and consuming active power until the operation completes. 8.3.1 reset/power-down rp# at v il initiates the reset/power-down mode. in read modes, rp#-low deselects the memory, places output drivers in a high-impedance state, and turns off numerous internal circuits. rp# must be held low for a minimum of t plph . time t phqv is required after return from reset mode until initial memory access outputs are valid. after this wake- up interval, normal operation is restored. the cui is reset to read array mode and status register is set to 0080h. during block erase, program, or lock-bit configuration modes, rp#-low will abort the operation. in default mode, sts transitions low and remains low for a maximum time of t plph + t phrh until the reset operation is complete. memory contents being altered are no longer valid; the data may be partially corrupted after a program or partially altered after an erase or lock-bit configuration. time t phwl is required after rp# goes to logic-high (v ih ) before another command can be written. as with any automated device, it is important to assert rp# during system reset. when the system comes out of reset, it expects to read from the flash memory. automated flash memories provide status information when accessed during block erase, program, or lock-bit configuration modes. if a cpu reset occurs with no flash memory reset, proper initialization may not occur because the flash memory may be providing status information instead of array data. intel ? flash memories allow proper initialization following a system reset through the use of the rp# input. in this application, rp# is controlled by the same reset# signal that resets the system cpu. 8.4 device commands when the v pen voltage v penlk , only read operations from the status register, cfi, identifier codes, or blocks are enabled. placing v penh on v pen additionally enables block erase, program, and lock-bit configuration operations. device operations are selected by writing specific commands to the command user interface (cui). the cui does not occupy an addressable memory location. it is the mechanism through which the flash device is controlled. .com .com .com .com 4 .com u datasheet
37 datasheet a command sequence is issued in two consecutive write cycles - a setup command followed by a confirm command. however, some commands are single-cycle commands consisting of a setup command only. generally, commands that alter the contents of the flash device, such as program or erase, require at least two write cycles to guard against inadvertent changes to the flash device. flash commands fall into two categories: basic commands and extended commands. basic commands are recognized by all intel ? flash devices, and are used to perform common flash operations such as selecting the read mode, programming the array, or erasing blocks. extended commands are product-dependant; they are used to perform additional features such as software block locking. table 18 describes all applicable commands on intel? embedded flash memory (j3 v. d). table 18. command bus operations for j3 v. d command setup write cycle confirm write cycle address bus data bus address bus data bus registers program enhanced configuration register register data 0060h register data 0004h program otp register device address 00c0h register offset register data clear status register device address 0050h --- --- program sts configuration register device address 00bs8h device address register data read modes read array device address 00ffh --- --- read status register device address 0070h --- --- read identifier codes (read device information) device address 0090h --- --- cfi query device address 0098h --- --- program and erase word/byte program device address 0040h/ 0010h device address array data buffered program word address 00e8h device address 00d0h block erase device address 0020h block address 00d0h program/erase suspend device address 00b0h --- --- program/erase resume device address 00d0h --- --- security lock block block address 0060h block address 0001h unlock block block address 0060h block address 00d0h .com .com .com .com 4 .com u datasheet
38 datasheet 9.0 flash operations this section describes the operational features of flash memory. operations are command-based, wherein command codes are first issued to the device, then the device performs the desired operation. all command codes are issued to the device using bus-write cycles (see chapter 8.0, ?bus interface? ). a complete list of available command codes can be found in appendix a, ?device command codes? . 9.1 status register the status register (sr) is an 8-bit, read-only register that indicates device status and operation errors. to read the status register, issue the read status register command. subsequent reads output status register information on dq[7:0], and 00h on dq[15:8]. sr status bits are set and cleared by the device. sr error bits are set by the device, but must be cleared using the clear status register command. upon power-up or exit from reset, the status register defaults to 80h. page-mode reads are not supported in this read mode. status register contents are latched on the falling edge of oe# or the first edge of cex that enables the device. oe# must toggle to v ih or the device must be disabled before further reads to update the status register latch. the read status register command functions independently of v pen voltage. table 19 shows status register bit definitions. table 19. status register bit definitions status register (sr) default value = 80h ready status erase suspend status erase error program error program /erase voltage error program suspend status block- locked error reserved 76543 2 1 0 bit name description 7 ready status 0 = device is busy; sr[6:0] are invalid (not driven); 1 = device is ready; sr[6:0] are valid. 6 erase suspend status 0 = erase suspend not in effect. 1 = erase suspend in effect. 5erase error command sequence error sr5 sr4 0 0 = program or erase operation successful. 0 1 = program error - operation aborted. 1 0 = erase error - operation aborted. 1 1 = command sequence error - command aborted. 4 program error 3 v pen error 0 = v pen within acceptable limits duri ng program or erase operation. 1 = v pen not within acceptable limit s during program or erase operation. operation aborted. 2 program suspend status 0 = program suspend not in effect. 1 = program suspend in effect. 1 block-locked error 0 = block not locked during program or erase - operation successful. 1 = block locked during program or erase - operation aborted. 0 reserved not used - reserved for future use. .com .com .com .com 4 .com u datasheet
39 datasheet 9.1.1 clearing the status register the status register (sr) contain status and error bits which are set by the device. sr status bits are cleared by the device, however sr error bits are cleared by issuing the clear status register command (see table 20 ). resetting the device also clears the status register. issuing the clear status register command places the device in read status register mode. note: care should be taken to avoid status register ambiguity. if a command sequence error occurs while in an erase suspend condition, the status register will indicate a command sequence error by setting sr4 and sr5. when the erase operation is resumed (and finishes), any errors that may have occurred during the erase operation will be masked by the command sequence error. to avoid this situation, clear the status register prior to resuming a suspended erase operation. the clear status register command functions independent of the voltage level on vpen. 9.2 read operations four types of data can be read from the device: array data, device information, cfi data, and device status. upon power-up or return from reset, the device defaults to read array mode. to change the device?s read mode, the appropriate command must be issued to the device. table 21 shows the command codes used to configure the device for the desired read mode. the following sections describe each read mode. 9.2.1 read array upon power-up or return from reset, the device defaults to read array mode. issuing the read array command places the device in read array mode. subsequent reads output array data on dq[15:0]. the device remains in read array mode until a different read command is issued, or a program or erase operation is performed, in which case, the read mode is automatically changed to read status. table 20. clear status register command bus-cycle command setup write cycle confirm write cycle address bus data bus address bus data bus clear status register device address 0050h --- --- table 21. read mode command bus-cycles command setup write cycle confirm write cycle address bus data bus address bus data bus read array device address 00ffh --- --- read status register device address 0070h --- --- read device information device address 0090h --- --- cfi query device address 0098h --- --- .com .com .com .com 4 .com u datasheet
40 datasheet to change the device to read array mode while it is programming or erasing, first issue the suspend command. after the operation has been suspended, issue the read array command. when the program or erase operation is subsequently resumed, the device will automatically revert back to read status mode. note: issuing the read array command to the device while it is actively programming or erasing causes subsequent reads from the device to output invalid data. valid array data is output only after the program or erase operation has finished. the read array command functions independent of the voltage level on vpen. 9.2.2 read status register issuing the read status register command places the device in read status register mode. subsequent reads output status register information on dq[7:0], and 00h on dq[15:8]. the device remains in read status register mode until a different read-mode command is issued. performing a program, erase, or block-lock operation also changes the device?s read mode to read status register mode. the status register is updated on the falling edge of ce#, or oe# when ce# is low. status register contents are valid only when sr7 = 1. when wsm us active, sr7 indicates the wsm?s state and sr[6:0] are in hig-z state. the read status register command functions independent of the voltage level on vpen. 9.2.3 read device information issuing the read device information command places the device in read device information mode. subsequent reads output device information on dq[15:0] (see table 22 ). the device remains in read device information mode until a different read command is issued. also, performing a program, erase, or block-lock operation changes the device to read status register mode. the read device information command functions independent of the voltage level on vpen. table 22. device information summary device information word address dq[15:0] device manufacturer code (intel) device base address + 00h 0089h device id code device base address + 01h (see appendix b, ?j3 v. d id codes? ) block lock status block base address + 02h dq0 = 0 unlocked dq0 = 1 locked dq[15:1] = rfu otp lock register device base address + 80h lock register 0 data otp register - factory segment device base address + 81h to 84h factory-programmed data otp register - user-programmable segment de vice base address + 85h to 88h user data .com .com .com .com 4 .com u datasheet
41 datasheet 9.2.4 cfi query the query table contains an assortment of flash product information such as block size, density, allowable command sets, electrical specifications, and other product information. the data contained in this table conforms to the common flash interface (cfi) protocol. issuing the cfi query command places the device in cfi query mode. subsequent reads output cfi information on dq[15:0] (see appendix d, ?common flash interface? ). the device remains in cfi query mode until a different read command is issued, or a program or erase operation is performed, which changes the read mode to read status register mode. the cfi query command functions independent of the voltage level on vpen. 9.3 programming operations programming the flash array changes ?ones? to ?zeros?. to change zeros to ones, an erase operation must be performed (see section 9.4, ?block erase operations? ). only one programming operation can occur at a time. programming is permitted during an erase suspend. information is programmed into the flash array by issuing the appropriate command. j3 v. d supports two different programming methods: byte/word and write-to-buffer. table 24 shows the two-cycle command sequences used for each method. note: all programming operations require the addressed block to be unlocked, and a valid vpen voltage applied throughout the programming operation. otherwise, the programming operation will abort, setting the appropriate status register error bit(s). the following sections describe each programming method. 9.3.1 single-word/byte programming array programming is performed by first issuing the single-word/byte program command. this is followed by writing the desired data at the desired array address. the read mode of the device is automatically changed to read status register mode, which remains in effect until another read- mode command is issued. during programming, sts and the status register indicate a busy status (sr7 = 0). upon completion, sts and the status register indicate a ready status (sr7 = 1). the status register should be checked for any errors (sr4), then cleared. table 24. program command bus-cycles command setup write cycle confirm write cycle address bus data bus address bus data bus single-word/byte program device address 0040h/0010h device address array data buffered program device address 00e8h device address 00d0h .com .com .com .com 4 .com u datasheet
42 datasheet note: issuing the read array command to the device while it is actively programming causes subsequent reads from the device to output invalid data. valid array data is output only after the program operation has finished. standby power levels are not be realized until the programming operation has finished. also, asserting rp# aborts the programming operation, and array contents at the addressed location are indeterminate. the addressed block should be erased, and the data re-programmed. if a single- word/byte program is attempted when the corresponding block lock-bit is set, sr1 and sr4 will be set. 9.3.2 buffered programming buffered programming operations simultaneous program multiple words into the flash memory array, significantly reducing effective word-write times. user-data is first written to a write buffer, then programmed into the flash memory array in buffer-size increments. appendix c, ?flow charts? contains a flow chart of the buffered-programming operation. note: optimal performance and power consumption is realized only by aligning the start address on 32- word boundaries (i.e., a[4:0] = 0b00000). crossing a 32-word boundary during a buffered programming operation can cause programming time to double. to perform a buffered programming operation, first issue the buffered program setup command at the desired starting address. the read mode of the device/addressed partition is automatically changed to read status register mode. polling sr7 determines write-buffer availability (0 = not available, 1 = available). if the write buffer is not available, re-issue the setup command and check sr7; repeat until sr7 = 1. next, issue the word count at the desired starting address. the word count represents the total number of words to be written into the write buffer, minus one. this value can range from 00h (one word) to a maximum of 1fh (32 words). exceeding the allowable range causes an abort. following the word count, the write buffer is filled with user-data. subsequent bus-write cycles provide addresses and data, up to the word count. all user-data addresses must lie between and , otherwise the wsm continues to run as normal but, user may advertently change the content in unexpected address locations. note: user-data is programmed into the flash array at the address issued when filling the write buffer. after all user-data is written into the write buffer, issue the confirm command. if a command other than the confirm command is issued to the device, a command sequence error occurs and the operation aborts. after issuing the confirm command, write-buffer contents are programmed into the flash memory array. the status register indicates a busy status (sr7 = 0) during array programming. note: issuing the read array command to the device while it is actively programming or erasing causes subsequent reads from the device to output invalid data. valid array data is output only after the program or erase operation has finished. upon completion of array programming, the status register indicates ready (sr7 = 1). a full status register check should be performed to check for any programming errors, then cleared by using the clear status register command. .com .com .com .com 4 .com u datasheet
43 datasheet additional buffered programming operations can be initiated by issuing another setup command, and repeating the buffered programming bus-cycle sequence. however, any errors in the status register must first be cleared before another buffered programming operation can be initiated. 9.4 block erase operations erasing a block changes ?zeros? to ?ones?. to change ones to zeros, a program operation must be performed (see section 9.3, ?programming operations? ). erasing is performed on a block basis - an entire block is erased each time an erase command sequence is issued. once a block is fully erased, all addressable locations within that block read as logical ones (ffffh). only one block- erase operation can occur at a time, and is not permitted during a program suspend. to perform a block-erase operation, issue the block erase command sequence at the desired block address. table 25 shows the two-cycle block erase command sequence. note: a block-erase operation requires the addressed block to be unlocked, and a valid voltage applied to vpen throughout the block-erase operation. otherwise, the operation will abort, setting the appropriate status register error bit(s). the erase confirm command latches the address of the block to be erased. the addressed block is preconditioned (programmed to all zeros), erased, and then verified. the read mode of the device is automatically changed to read status register mode, and remains in effect until another read-mode command is issued. during a block-erase operation, sts and the status register indicates a busy status (sr7 = 0). upon completion, sts and the status register indicates a ready status (sr7 = 1). the status register should be checked for any errors, then cleared. if any errors did occur, subsequent erase commands to the device are ignored unless the status register is cleared. the only valid commands during a block erase operation are read array, read device information, cfi query, and erase suspend. after the block-erase operation has completed, any valid command can be issued. note: issuing the read array command to the device while it is actively erasing causes subsequent reads from the device to output invalid data. valid array data is output only after the block-erase operation has finished. standby power levels are not be realized until the block-erase operation has finished. also, asserting rp# aborts the block-erase operation, and array contents at the addressed location are indeterminate. the addressed block should be erased before programming within the block is attempted. table 25. block-erase command bus-cycle command setup write cycle confirm write cycle address bus data bus address bus data bus block erase device address 0020h block address 00d0h .com .com .com .com 4 .com u datasheet
44 datasheet 9.5 suspend and resume an erase or programming operation can be suspended to perform other operations, and then subsequently resumed. table 26 shows the suspend and resume command bus-cycles. note: all erase and programming operations require the addressed block to remain unlocked with a valid voltage applied to vpen throughout the suspend operation. otherwise, the block-erase or programming operation will abort, setting the appropriate status register error bit(s). also, asserting rp# aborts suspended block-erase and programming operations, rendering array contents at the addressed location(s) indeterminate. to suspend an on-going erase or program operation, issue the suspend command to any device address. the program or erase operation suspends at pre-determined points during the operation after a delay of t susp . suspend is achieved when sts (in ry/by# mode) goes high, sr[7,6] = 1 (erase-suspend) or sr[7,2] = 1 (program-suspend). note: issuing the suspend command does not change the read mode of the device. the device will be in read status register mode from when the erase or program command was first issued, unless the read mode was changed prior to issuing the suspend command. not all commands are allowed when the device is suspended. table 27 shows which device commands are allowed during program suspend or erase suspend. table 26. suspend and resume command bus-cycles command setup write cycle confirm write cycle address bus data bus address bus data bus suspend device address 00b0h --- --- resume device address 00d0h --- --- table 27. valid commands during suspend (sheet 1 of 2) device command program suspend erase suspend sts configuration allowed allowed read array allowed allowed read status register allowed allowed clear status register allowed allowed read device information allowed allowed cfi query allowed allowed word program not allowed allowed buffered program not allowed allowed block erase not allowed not allowed program suspend not allowed allowed erase suspend not allowed not allowed program/erase resume allowed allowed .com .com .com .com 4 .com u datasheet
45 datasheet during suspend, array-read operations are not allowed in blocks being erased or programmed. a block-erase under program-suspend is not allowed. however, word-program under erase- suspend is allowed, and can be suspended. this results in a simultaneous erase-suspend/ program- suspend condition, indicated by sr[7,6,2] = 1. to resume a suspended program or erase operation, issue the resume command to any device address. the read mode of the device is automatically changed to read status register. the operation continues where it left off, sts (in ry/by# mode) goes low, and the respective status register bits are cleared. when the resume command is issued during a simultaneous erase-suspend/ program-suspend condition, the programming operation is resumed first. upon completion of the programming operation, the status register should be checked for any errors, and cleared. the resume command must be issued again to complete the erase operation. upon completion of the erase operation, the status register should be checked for any errors, and cleared. 9.6 status signal (sts) the status (sts) signal can be configured to different states using the sts configuration command. once the sts signal has been configured, it remains in that configuration until another configuration command is issued or rp# is asserted low. initially, the sts signal defaults to ry/ by# operation where ry/by# low indicates that the wsm is busy. ry/by# high indicates that the state machine is ready for a new operation or suspended. table 29 displays possible sts configurations. notes: 1. in case of 256 mb device (2x128), the command sequence must be repeated for each die at its base address 2. in case of 256 mb device (2x128), keep the second cycle to the same address. (ie. do not toggle a24 for the second cycle) to reconfigure the status (sts) signal to other modes, the configuration command is given followed by the desired configuration code. the three alternate configurations are all pulse mode for use as a system interrupt as described in the following paragraphs. for these configurations, bit 0 controls erase complete interrupt pulse, and bit 1 controls program complete interrupt pulse. supplying the 0x00 configuration code with the configuration command resets the sts signal to lock block not allowed not allowed unlock block not allowed not allowed program otp register not allowed not allowed table 27. valid commands during suspend (sheet 2 of 2) device command program suspend erase suspend table 28. sts configuration register command setup write cycle confirm write cycle address bus data bus address bus data bus sts configuration device address 1 00b8h device address 2 register data .com .com .com .com 4 .com u datasheet
46 datasheet the default ry/by# level mode. the configuration command may only be given when the device is not busy or suspended. check sr.7 for device status. an invalid configuration code will result in sr.4 and sr.5 being set. note: sts pulse mode is not supported in the clear lock bits and set lock bit commands 9.7 security and protection intel? embedded flash memory (j3 v. d) device offer both hardware and software security features. block lock operations, prs and vpen allow users to implement various levels of data protection. 9.7.1 normal block locking j3 v. d has the unique capability of flexible block locking (locked blocks remain locked upon reset or power cycle): all blocks are unlocked at the factory. blocks can be locked individually by issuing the set block lock bit command sequence to any address within a block. once locked, blocks remain locked when power is removed, or when the device is reset. table 29. sts configuration coding definitions d7 d6 d5 d4 d3 d2 d1 d0 reserved pulse on program complete (1) pulse on erase complete (1) d[1:0] = sts configuration codes notes 00 = default, level mode; device ready indication controls hold to a memory controller to prevent accessing a flash memory subsystem while any flash device's wsm is busy. 01 = pulse on erase complete generates a system interrupt pulse when any flash device in an array has completed a block erase. helpful for reformatting blocks after file system free space reclamation or ?cleanup.? 10 = pulse on program complete not supported on this device. 11 = pulse on erase or program complete generates system interrupts to trigger servicing of flash arrays when either erase or program operations are completed, when a common interrupt service routine is desired. notes: 1. when configured in one of the pulse modes, sts pulses low with a typical pulse width of 500 ns. 2. an invalid configuration code will result in both sr4 and sr5 being set. 3. reserved bits are invalid should be ignored. .com .com .com .com 4 .com u datasheet
47 datasheet all locked blocks are unlocked simultaneously by issuing the clear block lock bits command sequence to any device address. locked blocks cannot be erased or programmed. table 30 summarizes the command bus-cycles. after issuing the set block lock bit setup command or clear block lock bits setup command, the device?s read mode is automatically changed to read status register mode. after issuing the confirm command, completion of the operation is indicated by sts (in ry/by# mode) going high and sr7 = 1. blocks cannot be locked or unlocked while programming or erasing, or while the device is suspended. reliable block lock and unlock operations occur only when v cc and v pen are valid. when v pen v penlk , block lock-bits cannot be changed. when the set lock-bit operation is complete, sr4 should be checked for any error. when the clear lock-bit operation is complete, sr5 should be checked for any error. errors bits must be cleared using the clear status register command. block lock-bit status can be determined by first issuing the read device information command, and then reading from + 02h. dq0 indicates the lock status of the addressed block (0 = unlocked, 1 = locked). 9.7.2 configurable block locking one of the unique new features on the j3 v. d, non-existent on the previous generations of this product family, is the ability to protect and/or secure the user?s system by offering multiple level of securities: non-volatile temporary; non-volatile semi-permanently or non-volatile permanently. for additional information and collateral request, please contact your filed representative. 9.7.3 otp protection registers j3 v. d includes a 128-bit protection register (pr) that can be used to increase the security of a system design. for example, the number contained in the pr can be used to ?match? the flash component with other system components such as the cpu or asic, hence preventing device substitution. the 128-bits of the pr are divided into two 64-bit segments: ? one segment is programmed at the intel factory with a unique unalterable 64-bit number. ? the other segment is left blank for customer designers to program as desired. once the customer segment is programmed, it can be locked to prevent further programming. table 30. block locking command bus-cycles command setup write cycle confirm write cycle address bus data bus address bus data bus set block lock bit block address 0060h block address 0001h clear block lock bits device address 0060h device address 00d0h .com .com .com .com 4 .com u datasheet
48 datasheet 9.7.4 reading the otp protection register the protection register is read in identification read mode. the device is switched to this mode by issuing the read identifier command (0090h). once in this mode, read cycles from addresses shown in table 31 or table 32 retrieve the specified information. to return to read array mode, write the read array command (00ffh). 9.7.5 programming the otp protection register protection register bits are programmed using the two-cycle protection program command. the 64-bit number is programmed 16 bits at a time for word-wide configuration and eight bits at a time for byte-wide configuration. first write the protection program setup command, 00c0h. the next write to the device will latch in address and data and program the specified location. the allowable addresses are shown in table 31, ?word-wide protection register addressing? on page 49 or table 32, ?byte-wide protection register addressing? on page 50 . see figure 24, ?protection register programming flowchart? on page 61 . any attempt to address protection program commands outside the defined pr address space will result in a status register error (sr.4 will be set). attempting to program a locked pr segment will result in a status register error (sr.4 and sr.1 will be set). 9.7.6 locking the otp protection register the user-programmable segment of the protection register is lockable by programming bit 1 of the protection lock register (plr) to 0. bit 0 of this location is programmed to 0 at the intel factory to protect the unique device number. bit 1 is set using the protection program command to program ?0xfffd? to the plr. after these bits have been programmed, no further changes can be made to the values stored in the protection register. protection program commands to a locked section will result in a status register error (sr.4 and sr.1 will be set). pr lockout state is not reversible. note: a0 is not used in x16 mode when accessing the protection register map. see table 31 for x16 addressing. if x8 mode a0 is used, see table 32 for x8 addressing. figure 15. protection register memory map 0x88 0x85 64-bit segment (user-programmable) 0x84 0x81 0x80 lock register 0 64-bit segment (factory-programmed) 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 128-bit protection register 0 word address a[23:1]: 128 mbit a[21:1]: 32 mbit a[22:1]: 64 mbit a[24:1]: 256 mbit .com .com .com .com 4 .com u datasheet
49 datasheet table 31. word-wide protection register addressing word use a8a7a6a5a4a3a2a1 lock both 10000000 0 factory10000001 1 factory10000010 2 factory10000011 3 factory10000100 4 user 10000101 5 user 10000110 6 user 10000111 7 user 10001000 note: all address lines not specified in the above table must be 0 when accessing the protection register (i.e., a[max:9] = 0.) .com .com .com .com 4 .com u datasheet
50 datasheet 9.7.7 vpp/ vpen protection when it?s necessary to protect the entire array, global protection can be achieved using a hardware mechanism. using vpp or vpen. whenever a valid voltage is present on vpp or vpen, blocks within the main flash array can be erased or programmed. by grounding vpp or vpen, blocks within the main array cannot be altered ? attempts to program or erase blocks will fail resulting in the setting of the appropriate error bit in the status register. by holding vpp or vpen low, absolute write protection of all blocks in the array can be achieved. table 32. byte-wide protection register addressing byteusea8a7a6a5a4a3a2a1a0 lockboth100000000 lockboth100000001 0factory100000010 1factory100000011 2factory100000100 3factory100000101 4factory100000110 5factory100000111 6factory100001000 7factory100001001 8user100001010 9user100001011 auser100001100 buser100001101 cuser100001110 duser100001111 euser100010000 fuser100010001 note: all address lines not specified in the above table must be 0 when accessing the protection register, i.e., a[max:9] = 0. .com .com .com .com 4 .com u datasheet
51 datasheet appendix a device command codes for a complete definition on device operations refer to section 8.4, ?device commands? on page 36 . the list of all applicable commands are included here one more time for the conveninece. table 33. command bus operations for j3 v. d command setup write cycle confirm write cycle address bus data bus address bus data bus registers program enhanced configuration register register data 0060h register data 0004h program otp register device address 00c0h register offset register data clear status register device address 0050h --- --- program sts configuration register device address 00b8h --- --- read modes read array device address 00ffh --- --- read status register device address 0070h --- --- read identifier codes (read device information) device address 0090h --- --- cfi query device address 0098h --- --- program and erase word/byte program device address 0040h/ 0010h device address array data buffered program word address 00e8h device address 00d0h block erase device address 0020h block address 00d0h program/erase suspend device address 00b0h --- --- program/erase resume device address 00d0h --- --- security lock block block address 0060h block address 0001h unlock block block address 0060h block address 00d0h .com .com .com .com 4 .com u datasheet
52 datasheet appendix b j3 v. d id codes table 34. read identifier codes code address data device code 32-mbit 00001 0016 64-mbit 00001 0017 128-mbit 00001 0018 .com .com .com .com 4 .com u datasheet
53 datasheet appendix c flow charts c.1 write to buffer figure 16. write to buffer flowchart start setup - write 0xe8 - block address check buffer status - perform read operation - read ready status on signal sr7 sr7 = 1? word count - address = block address - data = word count minus 1 (valid range = 0x00 to 0x1f) confirm - write 0xd0 - block address end yes no yes sr7 = 1? no load buffer - fill write buffer up to word count - address = within buffer range - data = user data read status register (sr) full status register check (if desired) .com .com .com .com 4 .com u datasheet
54 datasheet c.2 status register figure 17. status register flowchart start sr7 = '1' sr2 = '1' sr4 = '1' sr3 = '1' sr1 = '1' yes yes yes no no no no sr6 = '1' yes no sr5 = '1' no no error command sequence yes yes yes error erase failure error program failure - set by wsm - reset by user - see clear status register command - set/reset by wsm sr4 = '1' yes no end command cycle - issue status register command - address = any dev ice address - data = 0x70 erase suspend see suspend/resume flowchart program suspend see suspend/resume flowchart error v pen < v penlk error block locked data cycle - read status register sr[7:0] .com .com .com .com 4 .com u datasheet
55 datasheet c.3 byte/word programming figure 18. byte/word program flowchart start write 40h, address write data and address read status register sr.7 = full status check if desired byte/word program complete read status register data (see above) voltage range error device protect error programming error byte/word program successful sr.3 = sr.1 = sr.4 = full status check procedure bus operation write write standby 1. toggling oe# (low to high to low) updates the status register. this can be done in place of issuing the read status register command. repeat for subsequent programming operations. sr full status check can be done after each program operation, or after a sequence of programming operations. write ffh after the last program operation to place device in read array mode. bus operation standby standby toggling oe# (low to high to low) updates the status register. this can be done in place of issuing the read status register command. repeat for subsequent programming operations. sr.4, sr.3 and sr.1 are only cleared by the clear status register command in cases where multiple locations are programmed before full status is checked. if an error is detected, clear the status register before attempting retry or other error recovery. 0 1 1 0 1 0 1 0 command setup byte/ word program byte/word program comments data = 40h addr = location to be programmed data = data to be programmed addr = location to be programmed check sr.7 1 = wsm ready 0 = wsm busy command comments check sr.3 1 = programming to voltage error detect check sr.4 1 = programming error read (note 1) status register data standby check sr.1 1 = device protect detect rp# = v ih , block lock-bit is set only required for systems implemeting lock-bit configuration. .com .com .com .com 4 .com u datasheet
56 datasheet c.4 program suspend/resume figure 19. program suspend/resume flowchart start write b0h read status register sr.7 = sr.2 = programming completed write d0h programming resumed write ffh read array data 1 1 0 0 bus operation command comments write program suspend data = b0h addr = x read status register data addr = x standby check sr.7 1 - wsm ready 0 = wsm busy standby check sr.6 1 = programming suspended 0 = programming completed read read array locations other than that being programmed. write ffh read data array done reading yes no write read array data = ffh addr = x write program resume data = d0h addr = x .com .com .com .com 4 .com u datasheet
57 datasheet c.5 block erase figure 20. block erase flowchart start read status register sr.7 = erase flash block(s) complete 0 1 full status check if desired suspend erase issue single block erase command 20h, block address suspend erase loop write confirm d0h block address yes no bus operation command comments write erase block data = 20h addr = block address write (note 1) erase confirm data = d0h addr = block address read status register data with the device enabled, oe# low updates sr addr = x standby check sr.7 1 = wsm ready 0 = wsm busy 1. the erase confirm byte must follow erase setup. this device does not support erase queuing. please see application note ap-646 for software erase queuing compatibility. full status check can be done after all erase and write sequences complete. write ffh after the last operation to reset the device to read array mode. .com .com .com .com 4 .com u datasheet
58 datasheet c.6 block erase suspend/resume figure 21. block erase suspend/resume flowchart start write b0h read status register sr.7 = sr.6 = block erase completed read or program? done? write d0h block erase resumed write ffh read array data program program loop read array data read no yes 1 1 0 0 bus operation command comments write erase suspend data = b0h addr = x read status register data addr = x standby check sr.7 1 - wsm ready 0 = wsm busy standby check sr.6 1 = block erase suspended 0 = block erase completed write erase resume data = d0h addr = x .com .com .com .com 4 .com u datasheet
59 datasheet c.7 block locking figure 22. set block lock-bit flowchart start write 60h, block address write 01h, block address read status register sr.7 = full status check if desired set lock-bit complete full status check procedure bus operation write 1 0 command set block lock-bit setup comments data = 60h addr =block address read status register data (see above) voltage range error sr.3 = 1 0 command sequence error sr.4,5 = 1 0 set lock-bit error sr.4 = 1 0 set lock-bit successful bus operation standby command comments check sr.3 1 = programming voltage error detect sr.5, sr.4 and sr.3 are only cleared by the clear status register command, in cases where multiple lock-bits are set before full status is checked. if an error is detected, clear the status register before attempting retry or other error recovery. standby check sr.4, 5 both 1 = command sequence error standby check sr.4 1 = set lock-bit error write set block lock-bit confirm data = 01h addr = block address standby repeat for subsequent lock-bit operations. full status check can be done after each lock-bit set operation or after a sequence of lock-bit set operations. write ffh after the last lock-bit set operation to place device in read array mode. check sr.7 1 = wsm ready 0 = wsm busy read status register data .com .com .com .com 4 .com u datasheet
60 datasheet c.8 unlock block figure 23. clear lock-bit flowchart start write 60h write d0h read status register sr.7 = full status check if desired clear block lock-bits complete full status check procedure bus operation write write standby write ffh after the clear lock-bits operation to place device in read array mode. bus operation standby sr.5, sr.4, and sr.3 are only cleared by the clear status register command. if an error is detected, clear the status register before attempting retry or other error recovery. 1 0 command clear block lock-bits setup clear block or lock-bits confirm comments data = 60h addr = x data = d0h addr = x check sr.7 1 = wsm ready 0 = wsm busy command comments check sr.3 1 = programming voltage error detect read status register data (see above) voltage range error sr.3 = 1 0 command sequence error sr.4,5 = 1 0 clear block lock-bits error sr.5 = 1 0 read status register data standby check sr.4, 5 both 1 = command sequence error standby check sr.5 1 = clear block lock-bits error clear block lock-bits successful .com .com .com .com 4 .com u datasheet
61 datasheet c.9 otp protection register programming figure 24. protection register programming flowchart start write c0h (protection reg. program setup) write protect. register address/data read status register sr.7 = 1? full status check if desired program complete read status register data (see above) v pen range error protection register programming error attempted program to locked register - aborted program successful sr.3, sr.4 = sr.1, sr.4 = sr.1, sr.4 = full status check procedure bus operation write write standby protection program operations can only be addressed within the protection register address space. addresses outside the defined space will return an error. repeat for subsequent programming operations. sr full status check can be done after each program or after a sequence of program operations. write ffh after the last program operation to reset device to read array mode. bus operation standby standby sr.3 must be cleared, if set during a program attempt, before further attempts are allowed by the write state machine. sr.1, sr.3 and sr.4 are only cleared by the clear staus register command, in cases of multiple protection register program operations before full status is checked. if an error is detected, clear the status register before attempting retry or other error recovery. no yes 1, 1 0,1 1,1 command protection program setup protection program comments data = c0h data = data to program addr = location to program check sr.7 1 = wsm ready 0 = wsm busy command comments sr.1 sr.3 sr.4 0 1 1 v pen low 0 0 1 prot. reg. prog. error 1 0 1 register locked: aborted read status register data toggle ce# or oe# to update status register data standby .com .com .com .com 4 .com u datasheet
62 datasheet appendix d common flash interface the common flash interface(cfi) specification outlines device and host system software interrogation handshake which allows specific vendor-specified software algorithms to be used for entire families of devices. this allows device independent, jedec id-independent, and forward- and backward-compatible software support for the specified flash device families. it allows flash vendors to standardize their existing interfaces for long-term compatibility. this appendix defines the data structure or ?database? returned by the common flash interface (cfi) query command. system software should parse this structure to gain critical information such as block size, density, x8/x16, and electrical specifications. once this information has been obtained, the software will know which command sets to use to enable flash writes, block erases, and otherwise control the flash component. the query is part of an overall specification for multiple command set and control interface descriptions called common flash interface, or cfi. d.1 query structure output the query ?database? allows system software to gain information for controlling the flash component. this section describes the device?s cfi-compliant interface that allows the host system to access query data. query data are always presented on the lowest-order data outputs (d[7:0]) only. the numerical offset value is the address relative to the maximum bus width supported by the device. on this family of devices, the query table device starting address is a 10h, which is a word address for x16 devices. for a word-wide (x16) device, the first two bytes of the query structure, ?q? and ?r? in ascii, appear on the low byte at word addresses 10h and 11h. this cfi-compliant device outputs 00h data on upper bytes. thus, the device outputs ascii ?q? in the low byte (d[7:0]) and 00h in the high byte (d[15:8]). at query addresses containing two or more bytes of information, the least significant data byte is presented at the lower address, and the most significant data byte is presented at the higher address. in all of the following tables, addresses and data are represented in hexadecimal notation, so the ?h? suffix has been dropped. in addition, since the upper byte of word-wide devices is always ?00h,? the leading ?00? has been dropped from the table notation and only the lower byte value is shown. any x16 device outputs can be assumed to have 00h on the upper byte in this mode. .com .com .com .com 4 .com u datasheet
63 datasheet d.2 query structure overview the query command causes the flash component to display the common flash interface (cfi) query structure or ?database.? the structure sub-sections and address locations are summarized below. see ap-646 common flash interface (cfi) and command sets (order number 292204) for a full description of cfi. the following sections describe the query structure sub-sections in detail. table 35. summary of query structure output as a function of device and mode device type/ mode query start location in maximum device bus width addresses query data with maximum device bus width addressing query data with byte addressing hex offset hex code ascii value hex offset hex code ascii value x16 device 10h 10: 0051 ?q? 20: 51 ?q? x16 mode 11: 0052 ?r? 21: 00 ?null? 12: 0059 ?y? 22: 52 ?r? x16 device 20: 51 ?q? x8 mode n/a (1) n/a (1) 21: 51 ?q? 22: 52 ?r? note: 1. the system must drive the lowest order addresses to access all the device's array data when the device is configured in x8 mode. therefore, word addressing , where these lower addresses are not toggled by the system, is "not applicable" for x8-configured devices. table 36. example of query structure output of a x16- and x8-capable device word addressing byte addressing offset hex code value offset hex code value a 15 ?a 0 d15?d 0 a 7 ?a 0 d 7 ?d 0 0010h 0051 ?q? 20h 51 ?q? 0011h 0052 ?r? 21h 51 ?q? 0012h 0059 ?y? 22h 52 ?r? 0013h p_id lo prvendor 23h 52 ?r? 0014h p_id hi id # 24h 59 ?y? 0015h p lo prvendor 25h 59 ?y? 0016h p hi tbladr 26h p_id lo prvendor 0017h a_id lo altvendor 27h p_id lo id # 0018h a_id hi id # 28h p_id hi id # ... ... ... ... ... ... .com .com .com .com 4 .com u datasheet
64 datasheet d.3 block status register the block status register indicates whether an erase operation completed successfully or whether a given block is locked or can be accessed for flash program/erase operations. d.4 cfi query identification string the cfi query identification string provides verification that the component supports the common flash interface specification. it also indicates the specification version and supported vendor-specified command set(s). table 37. query structure offset sub-section name description notes 00h manufacturer code 1 01h device code 1 (ba+2)h (2) block status register block-specific information 1,2 04-0fh reserved reserved for vendor-specific information 1 10h cfi query identification string reserved for vendor-specific information 1 1bh system interface information command set id and vendor data offset 1 27h device geometry definition flash device layout 1 p (3) primary intel-specific extended query table vendor-defined additional information specific to the primary vendor algorithm 1,3 notes: 1. refer to the query structure output section and offset 28h for the detailed definition of offset address as a function of device bus width and mode. 2. ba = block address beginning location (i.e., 02000h is block 2?s beginning location when the block size is 128 kbyte). 3. offset 15 defines ?p? which points to the primary intel-specific extended query table. table 38. block status register offset length description address value (ba+2)h (1) 1 block lock status register ba+2: --00 or --01 bsr.0 block lock status 0 = unlocked 1 = locked ba+2: (bit 0): 0 or 1 bsr 1?15: reserved for future use ba+2: (bit 1?15): 0 note: 1. ba = the beginning location of a block address (i .e., 008000h is block 1?s (64-kb block) beginning location in word mode). table 39. cfi identification (sheet 1 of 2) offset length description add. hex code value 10h 3 query-unique ascii string ?qry? 10 --51 ?q? 11: --52 ?r? 12: --59 ?y? 13h 2 primary vendor command set and control interface id code. 13: --01 16-bit id code for vendor-specified algorithms 14: --00 15h 2 extended query table primar y algorithm address 15: --31 16: --00 17h 2 alternate vendor command set and control interface id code. 17: --00 .com .com .com .com 4 .com u datasheet
65 datasheet d.5 system interface information the following device information can optimize system interface software. 0000h means no second vendor-specified algorithm exists 18: --00 19h 2 secondary algorithm extended query table address. 19: --00 0000h means none exists 1a: --00 table 39. cfi identification (sheet 2 of 2) offset length description add. hex code value table 40. system interface information offset length description add. hex code value 1bh 1 v cc logic supply minimum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 bcd volts 1b: --27 2.7 v 1ch 1 v cc logic supply maximum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 bcd volts 1c: --36 3.6 v 1dh 1 v pp [programming] supply minimum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 hex volts 1d: --00 0.0 v 1eh 1 v pp [programming] supply maximum program/erase voltage bits 0?3 bcd 100 mv bits 4?7 hex volts 1e: --00 0.0 v 1fh 1 ?n? such that typical single word program time-out = 2 n s 1f: --06 64 s 20h 1 ?n? such that typical max. buffer write time-out = 2 n s 20: --07 128 s 21h 1 ?n? such that typical block erase time-out = 2 n ms 21: --0a 1 s 22h 1 ?n? such that typical full chip erase time-out = 2 n ms 22: --00 na 23h 1 ?n? such that maximum word program time-out = 2 n times typical 23: --02 256 s 24h 1 ?n? such that maximum buffer write time-out = 2 n times typical 24: --03 1024 s 25h 1 ?n? such that maximum block erase time-out = 2 n times typical 25: --02 4 s 26h 1 ?n? such that maximum chip erase time-out = 2 n times typical 26: --00 na .com .com .com .com 4 .com u datasheet
66 datasheet d.6 device geometry definition this field provides critical details of the flash device geometry. device geometry definition table 41. device geometry definition offset length description code see table below 27h 1 ?n? such that device size = 2 n in number of bytes 27: 28h 2 flash device interface: x8 async x16 async x8/x16 async 28: --02 x8/ x16 28:00,29:00 28:01,29:00 28:02,29:00 29: --00 2ah 2 ?n? such that maximum number of bytes in write buffer = 2 n 2a: --05 32 2b: --00 2ch 1 number of erase block regions within device: 1. x = 0 means no erase blocking; the device erases in ?bulk? 2. x specifies the number of device or partition regions with one or more contiguous same-size erase blocks 3. symmetrically blocked partitions have one blocking region 4. partition size = (total blocks) x (individual block size) 2c: --01 1 2dh 4 erase block region 1 information 2d: bits 0?15 = y, y+1 = number of identical-size erase blocks 2e: bits 16?31 = z, region erase block(s) size are z x 256 bytes 2f: 30: address 32 mbit 64 mbit 128 mbit 27: --16 --17 --18 28: --02 --02 --02 29: --00 --00 --00 2a: --05 --05 --05 2b: --00 --00 --00 2c: --01 --01 --01 2d: --1f --3f --7f 2e: --00 --00 --00 2f: --00 --00 --00 30: --02 --02 --02 .com .com .com .com 4 .com u datasheet
67 datasheet d.7 primary-vendor specific extended query table certain flash features and commands are optional. the primary vendor-specific extended query table specifies this and other similar information. table 42. primary vendor-specific extended query offset (1) p = 31h length description (optional flash features and commands) add. hex code value (p+0)h 3 primary extended query table 31: --50 ?p? (p+1)h unique ascii string ?pri? 32: --52 ?r? (p+2)h 33: --49 ?i? (p+3)h 1 major version number, ascii 34: --31 ?1? (p+4)h 1 minor version number, ascii 35: --31 ?1? (p+5)h (p+6)h (p+7)h (p+8)h 4 optional feature and command support (1=yes, 0=no) 36: --ce bits 9?31 are reserved; undefined bits are ?0.? if bit 31 is 37: --00 ?1? then another 31 bit field of optional features follows at 38: --00 the end of the bit-30 field. 39: --00 bit 0 chip erase supported bit 0 = 0 no bit 1 suspend erase supported bit 1 = 1 yes bit 2 suspend program supported bit 2 = 1 yes bit 3 legacy lock/unlock supported bit 3 = 1 (1) ye s (1) bit 4 queued erase supported bit 4 = 0 no bit 5 instant individual block locking supported bit 5 = 0 no bit 6 protection bits supported bit 6 = 1 yes bit 7 page-mode read supported bit 7 = 1 yes bit 8 synchronous read supported bit 8 = 0 no (p+9)h 1 supported functions after suspend: read array, status, query other supported operations are: bits 1?7 reserved; undefined bits are ?0? 3a: --01 bit 0 program supported after erase suspend bit 0 = 1 yes (p+a)h (p+b)h 2 block status register mask 3b: --01 bits 2?15 are reserved; undefined bits are ?0? 3c: --00 bit 0 block lock-bit status register active bit 0 = 1 yes bit 1 block lock-down bit status active bit 1 = 0 no (p+c)h 1 v cc logic supply highest performance program/erase voltage bits 0?3 bcd value in 100 mv bits 4?7 bcd value in volts 3d: --33 3.3 v (p+d)h 1 v pp optimum program/erase supply voltage bits 0?3 bcd value in 100 mv bits 4?7 hex value in volts 3e: --00 0.0 v note: 1. future devices may not support the described ?legacy lock/unlock? function. thus bit 3 would have a value of ?0.? .com .com .com .com 4 .com u datasheet
68 datasheet table 43. protection register information offset (1) p = 31h length description (optional flash features and commands) add. hex code value (p+e)h 1 number of protection register fields in jedec id space. ?00h,? indicates that 256 protection bytes are available 3f: --01 01 (p+f)h (p+10)h (p+11)h (p+12)h 4 protection field 1: protection description this field describes user-ava ilable one time programmable (otp) protection register by tes. some are pre-programmed with device-unique serial numbers. others are user- programmable. bits 0-15 point to the protection register lock byte, the section?s first byte. the following bytes are factory pre-programmed and user-programmable. bits 0-7 = lock/bytes jedec-plane physical low address bits 8-15 = lock/bytes jedec-plane physical high address bits 16-23 = ?n? such that 2 n = factory pre-programmed bytes bits 24-31 = ?n? such that 2 n = user-programmable bytes 40: 41: 42: 43: --80 --00 --03 --03 80h 00h 8bytes 8bytes note: 1. the variable p is a pointer which is defined at cfi offset 15h. table 44. burst read information offset (1) p = 31h length description (optional flash features and commands) add. hex code value (p+13)h 1 page mode read capability bits 0?7 = ?n? such that 2 n hex value represents the number of read-page bytes. see offset 28h for device word width to determine page-mode data output width. 00h indicates no read page buffer. 44: --03 8 byte (p+14)h 1 number of synchronous mode read configuration fields that follow. 00h indicates no burst capability. 45: --00 0 (p+15)h reserved for future use 46: note: 1. the variable p is a pointer which is defined at cfi offset 15h. .com .com .com .com 4 .com u datasheet
69 datasheet appendix e additional information order number document/tool 298130 intel ? strataflash? memory (j3); 28f128j3, 28f640j3, 28f320j3 specification update 298136 intel ? persistent storage manager (ipsm) user?s guide software manual 297833 intel ? flash data integrator (fdi) user?s guide software manual 290606 5 volt intel ? strataflash? memoryi28f320j5 and 28f640j5 datasheet 292204 ap-646 common flash interface (cfi) and command sets 253418 intel ? wireless communications and computing package user?s guide 1. call the intel literature center at (800) 548-4725 to request intel documentation. international customers should contact their local intel or distribution sales office. 2. visit the intel home page http://www.intel.com for technical documentation and tools. 3. for the most current information on intel? embedded flash memory (j3 v. d), visit http:// developer.intel.com/design/flash/isf. .com .com .com .com 4 .com u datasheet
70 datasheet appendix f ordering information figure 25. decoder:intel? embedded flash memory (j3 v. d) family d = intel? 0.13 micron lithography j = intel ? embedded flash memory p c 2 8 f 3 2 0 j 3 d - 7 5 access speed 75 ns product family device density 128 = x8/x16 (128 mbit) 640 = x8/x16 (64 mbit) 320 = x8/x16 (32 mbit) package te= 56-lead tsop (j3c, 803) js = pb-free 56-tsop rc = 64-ball easy bga pc = 64-ball pb-free easy bga product line designator for all intel? flash products voltage (v cc /v pen ) 3 = 3 v/3 v table 45. order information: intel? embedded flash memory (j3 v. d) family 56-lead tsop 64-ball easy bga TE28F128J3D-75 rc28f128j3d-75 te28f640j3d-75 rc28f640j3d-75 te28f320j3d-75 rc28f320j3d-75 js28f128j3d-75 pc28f128j3d-75 js28f640j3d-75 pc28f640j3d-75 js28f320j3d-75 pc28f320j3d-75 .com .com .com .com 4 .com u datasheet
i datasheet 1.0 introduction ............................................................................................................. 6 1.1 nomenclature .................................................................................................. 6 1.2 acronyms ........................................................................................................ 6 1.3 conventions .................................................................................................... 6 2.0 functional overview ............................................................................................ 8 2.1 block diagram............................................................................................... 10 2.2 memory map ................................................................................................. 11 3.0 package information .........................................................................................12 3.1 56-lead tsop package ............................................................................... 12 3.2 easy bga package....................................................................................... 13 4.0 ballouts and signal descriptions .................................................................15 4.1 easy bga ballout (32/64/128 mbit)............................................................... 15 4.2 56-lead tsop package pinout (32/64/128 mbit) ......................................... 16 4.3 signal descriptions........................................................................................ 17 5.0 maximum ratings and operating conditions ......................................... 19 5.1 absolute maximum ratings........................................................................... 19 5.2 operating conditions..................................................................................... 19 5.3 power up/down ............................................................................................ 20 5.3.1 power-up/down characteristics ...................................................... 20 5.3.2 power supply decoupling ................................................................ 20 5.4 reset ............................................................................................................. 20 6.0 electrical characteristics ................................................................................ 21 6.1 dc current specifications ............................................................................. 21 6.2 dc voltage specifications ............................................................................. 22 6.3 capacitance .................................................................................................. 23 7.0 ac characteristics ............................................................................................. 24 7.1 read specifications....................................................................................... 25 7.2 write specifications....................................................................................... 28 7.3 program, erase, block-lock specifications .................................................. 30 7.4 reset specifications...................................................................................... 30 7.5 ac test conditions ....................................................................................... 32 8.0 bus interface .........................................................................................................33 8.1 bus reads..................................................................................................... 34 8.1.1 asynchronous page mode read...................................................... 34 8.1.1.1 enhanced configuration register (ecr) ............................ 34 8.1.2 output disable.................................................................................. 35 8.2 bus writes ..................................................................................................... 35 8.3 standby ......................................................................................................... 36 8.3.1 reset/power-down .......................................................................... 36 8.4 device commands ........................................................................................ 36 9.0 flash operations ................................................................................................. 38 9.1 status register.............................................................................................. 38 9.1.1 clearing the status register ............................................................ 39 .com .com .com .com 4 .com u datasheet
ii datasheet 9.2 read operations ............................................................................................39 9.2.1 read array ........................................................................................39 9.2.2 read status register ........................................................................40 9.2.3 read device information...................................................................40 9.2.4 cfi query..........................................................................................41 9.3 programming operations ...............................................................................41 9.3.1 single-word/byte programming........................................................41 9.3.2 buffered programming ......................................................................42 9.4 block erase operations .................................................................................43 9.5 suspend and resume....................................................................................44 9.6 status signal (sts)........................................................................................45 9.7 security and protection ..................................................................................46 9.7.1 normal block locking .......................................................................46 9.7.2 configurable block locking...............................................................47 9.7.3 otp protection registers .................................................................47 9.7.4 reading the otp protection register ...............................................48 9.7.5 programming the otp protection register.......................................48 9.7.6 locking the otp protection register................................................48 9.7.7 vpp/ vpen protection ......................................................................50 appendix a device command codes ................................................................................. 51 appendix b j3 v. d id codes .................................................................................................. 52 appendix c flow charts ........................................................................................................... 53 c.1 write to buffer ................................................................................................53 c.2 status register...............................................................................................54 c.3 byte/word programming ................................................................................55 c.4 program suspend/resume............................................................................56 c.5 block erase ....................................................................................................57 c.6 block erase suspend/resume ......................................................................58 c.7 block locking .................................................................................................59 c.8 unlock block ..................................................................................................60 c.9 otp protection register programming..........................................................61 appendix d common flash interface ................................................................................. 62 d.2 query structure overview ..............................................................................63 d.3 block status register .....................................................................................64 d.4 cfi query identification string .......................................................................64 d.5 system interface information .........................................................................65 d.6 device geometry definition ...........................................................................66 d.7 primary-vendor specific extended query table ...........................................67 appendix e additional information ...................................................................................... 69 appendix f ordering information ......................................................................................... 70 .com .com .com 4 .com u datasheet

▲Up To Search▲

Price & Availability of TE28F128J3D

	To Download TE28F128J3D Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .